> ## Documentation Index
> Fetch the complete documentation index at: https://api-reference.hyperswitch.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Evaluate Routing Rule

> Evaluate the active routing rule for a merchant against a payment context. Returns the ordered list of gateways selected by the rule without consuming SR data.



## OpenAPI

````yaml decision_engine_openapi-specs.json POST /routing/evaluate
openapi: 3.1.0
info:
  title: Decision Engine
  description: >-
    Open-source payment gateway routing service by Juspay. Selects the optimal
    payment processor for each transaction in real-time using success-rate
    scoring, rule-based routing, and elimination logic.


    ## Authentication


    This API supports two authentication methods:


    1. **JWT Bearer Token** - For dashboard/user sessions
       - Header: `Authorization: Bearer <jwt_token>`
       - Obtain via `/auth/login` endpoint

    2. **API Key** - For service-to-service/programmatic access
       - Header: `x-api-key: DE_<64_char_hex>`
       - Create via `/api-key/create` endpoint

    Protected endpoints require one of these authentication methods.
  version: 1.4.0
  contact:
    name: Juspay
    url: https://github.com/juspay/decision-engine
  license:
    name: AGPL-3.0
    url: https://www.gnu.org/licenses/agpl-3.0.html
servers:
  - url: http://localhost:8080
    description: Local development
  - url: https://sandbox.hyperswitch.io
    description: 'Hyperswitch sandbox with x-feature: decision-engine'
security: []
tags:
  - name: Health
    description: Service liveness, readiness, and diagnostics
  - name: Auth
    description: Dashboard auth and merchant selection
  - name: API Keys
    description: Service-to-service API key management
  - name: Gateway Decision
    description: Core routing decision APIs
  - name: Score Feedback
    description: Feed transaction outcomes back to improve SR scoring
  - name: Merchant Account
    description: Merchant configuration management
  - name: Routing Rules
    description: Euclid declarative routing rules engine
  - name: Rule Configuration
    description: Service-level SR/elimination config
  - name: Config
    description: Routing key and dimension metadata
  - name: Analytics
    description: ClickHouse-backed analytics and audit reads
  - name: Compatibility
    description: Legacy compatibility routes
  - name: Connector Costs
  - name: Merchant Features
  - name: Autopilot
paths:
  /routing/evaluate:
    post:
      tags:
        - Routing Rules
      summary: Evaluate routing rule
      description: >-
        Evaluate the active routing rule for a merchant against a payment
        context. Returns the ordered list of gateways selected by the rule
        without consuming SR data.
      operationId: evaluateRoutingRule
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RoutingRequest'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RoutingEvaluateResponse'
      security:
        - BearerAuth: []
        - ApiKeyAuth: []
components:
  schemas:
    RoutingRequest:
      type: object
      required:
        - created_by
        - parameters
      description: >-
        Request body for POST /routing/evaluate
        (src/euclid/types.rs::RoutingRequest). No camelCase rename — snake_case
        field names.
      properties:
        payment_id:
          type: string
          nullable: true
        created_by:
          type: string
          example: test_merchant
        fallback_output:
          type: array
          nullable: true
          items:
            $ref: '#/components/schemas/ConnectorInfo'
          description: Used when the rule evaluation yields no eligible connector.
        parameters:
          type: object
          additionalProperties:
            $ref: '#/components/schemas/ValueType'
          description: >-
            Map of DSL parameter name (e.g. currency, amount, cardType) to its
            ValueType.
          example:
            currency:
              type: str_value
              value: USD
    RoutingEvaluateResponse:
      type: object
      properties:
        payment_id:
          type: string
          nullable: true
        status:
          type: string
        output:
          type: object
        evaluated_output:
          type: array
          items:
            $ref: '#/components/schemas/ConnectorInfo'
        eligible_connectors:
          type: array
          items:
            $ref: '#/components/schemas/ConnectorInfo'
    ConnectorInfo:
      type: object
      properties:
        gateway_name:
          type: string
        gateway_id:
          type: string
          nullable: true
    ValueType:
      type: object
      required:
        - type
      description: Euclid condition value. Tagged by `type`; `value` holds the payload.
      properties:
        type:
          type: string
          enum:
            - number
            - enum_variant
            - metadata_variant
            - str_value
            - global_ref
            - number_array
            - enum_variant_array
            - number_comparison_array
        value:
          description: >-
            Shape depends on `type`: number->integer,
            enum_variant/str_value/global_ref->string,
            number_array/enum_variant_array->array of number/string,
            number_comparison_array->array of comparisons.
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT token obtained from /auth/login
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: API key created via /api-key/create

````