Get Routing Config

August 3, 2026 · View on GitHub

Use case

Returns routing keys/dimensions used by the dashboard to build routing configuration forms.

Authentication

Protected. Send either Authorization: Bearer <jwt_token> or x-api-key: <api_key>. In sandbox, also send x-feature: decision-engine.

For local development, start with:

export BASE_URL=http://localhost:8080
export AUTH_HEADER="Authorization: Bearer <jwt_token>"
# Sandbox only:
# export BASE_URL=https://sandbox.hyperswitch.io
# export FEATURE_HEADER="x-feature: decision-engine"

Request

  • Method and path: GET /config/routing-keys
  • Parameters: none.
  • Body: No parameters or request body.

Example

Get routing keys

curl "$BASE_URL/config/routing-keys" \
  --header "$AUTH_HEADER"

Response

Returns a keys map of routing-key name → metadata (its type, and for enums the allowed values as a comma-separated string).

{
  "keys": {
    "payment_method_type": {
      "type": "enum",
      "values": "credit, debit, card, upi_collect, ...",
      "min_value": null,
      "max_value": null,
      "min_length": null,
      "max_length": null,
      "exact_length": null,
      "regex": null
    },
    "amount": {
      "type": "integer",
      "values": null,
      "min_value": null,
      "max_value": null,
      "min_length": null,
      "max_length": null,
      "exact_length": null,
      "regex": null
    }
  }
}

Notes

  • Use this to keep UI selectors aligned with backend-supported routing dimensions.
  • The exact set can vary as backend routing attributes evolve.