Reconcile an order's fulfillment orders with the order's routing, in place (addressed by the order)

The refresh of POST /v1/fulfillment-orders/:id/refresh addressed by the order itself: routes the open order lines again and reconciles every open fulfillment order by route key (matched ones adjusted to the open quantities, unmatched ones canceled, or closed at what they fulfilled, missing routes created). An order without a fulfillment order gets new ones for its open lines. Nothing is deleted and shipped quantities are never touched.

Scope: fulfillment:write, channel:write or admin. A permission group made before the Channel API scopes existed grants it as fulfillment-orders:manage.

Idempotency: send Idempotency-Key; a retry with the same key replays the first answer.

Rate limit: write class, 1,200 requests per minute per tenant by default (read class 6,000). Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset; a refusal is 429 rate_limited with Retry-After.

Path Params
string
required
length between 1 and 300

The uuid, a legacy 24-hex id, or ext:: (URL-encoded).

Body Params
boolean
Headers
string
length between 7 and 50

Any string of 7 to 50 characters that identifies this request (an order number, a webhook id). A retry with the same key and the same body answers the first result with Idempotent-Replayed: true; the same key with a different body is 422 idempotency_key_reused; a concurrent request with the same key is 409 in_progress with Retry-After. Recommended on every write.

Responses

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json