Routing - Activate config

Activate a routing configuration.

Request

POST /routing/{routing_algorithm_id}/activate

cURL

curl

curl --request POST \
  --url https://sandbox.hyperswitch.io/routing/{routing_algorithm_id}/activate \
  --header 'api-key: <api-key>'

Authorization

• Header: api-key (string) — required

Use the API key created under your merchant account from the HyperSwitch dashboard. API key is used to authenticate API requests from your merchant server only. Don't expose this key on a website or embed it in a mobile application.

Path Parameters

• routing_algorithm_id (string) — required The unique identifier for a config.

Response

Status: 200 — application/json Routing config activated

Response (application/json)

{
  "id": "<string>",
  "profile_id": "<string>",
  "name": "<string>",
  "kind": "single",
  "description": "<string>",
  "created_at": 123,
  "modified_at": 123,
  "algorithm_for": "payment",
  "decision_engine_routing_id": "<string>"
}

Response fields

• id (string) — required

• profile_id (string) — required

• name (string) — required

• kind (enum) — required Available options: single, priority, volume_split, advanced, dynamic, three_ds_decision_rule

• description (string) — required

• created_at (integer) — required

• modified_at (integer) — required

• algorithm_for (enum) Available options: payment, payout, three_ds_authentication

• decision_engine_routing_id (string | null)

---

Suggest edits: https://github.com/juspay/hyperswitch/edit/main/api-reference/v1/routing/routing--activate-config.mdx Raise issue: https://github.com/juspay/hyperswitch/issues/new?title=Issue%20on%20docs&body=Path:%20/v1/routing/routing--activate-config

Related:

• Routing - Retrieve: https://api-reference.hyperswitch.io/v1/routing/routing--retrieve

• Routing - Evaluate: https://api-reference.hyperswitch.io/v1/routing/routing--evaluate