Update a Routing
Routing
Update a Routing
Replaces the routing’s full configuration.
PATCH
Update a Routing
Replaces the routing’s full configuration. The body has the same shape as Create a Routing — the new
default_route and condition_sets[] entirely supersede the previous live state. There is no field-level merge.
account_code and payment_method are sticky to the routing_id — they’re set at creation and cannot be changed by PATCH.
Path Parameters
The id returned by Create a Routing.
Response
Unique identifier for the routing.
Unique code for the account.
The payment method this routing applies to (e.g.,
CARD).Label for the routing.
The default routing logic.
Optional conditional logic.
ISO 8601 timestamp.
ISO 8601 timestamp.
Errors
| HTTP | code | When |
|---|---|---|
404 | ROUTING_NOT_FOUND | Unknown routing_id, or id belongs to a different account. |
400 | ROUTING_VALIDATION_FAILED | Schema or rule violation. |
400 | ROUTING_PROVIDER_NOT_AVAILABLE | A step references an inactive/unknown connection. |
400 | ROUTING_PAYMENT_METHOD_IMMUTABLE | Body’s payment_method doesn’t match the routing’s payment_method. |
409 | ROUTING_VERSION_CONFLICT | Another concurrent PATCH won the publish race. |
403 | INSUFFICIENT_SCOPE | API key missing routing:write. |
Authorizations
Headers
Path Parameters
Body
application/json
Response
OK
Example:
"r_8f2c1d3e-4b5a-6c7d-8e9f-0a1b2c3d4e5f"
Example:
"acc-uuid"
Example:
"CARD"
Example:
"Updated Card routing v2"
Example:
"2026-05-12T14:30:00Z"
Example:
"2026-05-12T14:30:00Z"