Activate a fulfillment route

POST 
/fulfillment-routes/:id/activate

Set the route as active. Active published routes are evaluated by the matcher.

Request

Responses

200

202

The merchant is entitled but its OMS environment is not provisioned yet. Provisioning has been kicked off (exactly once) and is in progress; retry the request — it succeeds once the environment is ready. Returned only for identity-token (dashboard) requests bound to an active-entitled merchant, not for secret-key API calls; any such endpoint can return it while provisioning is underway.

400

The request was rejected. type is invalid_request_error; when the failure is a validation failure code is validation_failed and errors lists every problem found, with field-attributable entries prefixed by the field’s path.

401

No credentials were supplied, or the identity token / secret key is not valid for the target merchant. type is authentication_error.

403

The credentials are valid but lack the permission this operation requires. type is permission_error.

404

No resource exists with the requested identifier. type is not_found_error.

429

Too many requests. The rate limit is applied per client across all operations. type is rate_limit_error.

500

The request could not be completed because of an unexpected error. type is api_error.

503

A dependency needed to serve the request is temporarily unavailable — for every operation the auth service that verifies credentials and resolves entitlement, and on the provisioning routes also the ODUS API the OMS reconciles against. type is api_error. Unlike a plain 500 the condition is transient rather than a fault in the request, so it is worth retrying with backoff.

504

The request exceeded the processing time limit and was abandoned. type is api_error and code is timeout — unlike a plain 500 the request may still have taken effect.