Acknowledge Order
POST/api/3pl/orders/:fulfillmentOrder/acknowledge
OPTIONAL pull-provider acknowledgment. After the partner has downloaded an order (the List Orders poll marks each served order as "downloaded" / request_status = accepted), the partner may explicitly acknowledge it — "we have it and will ship it" — advancing it to request_status = acknowledged and stamping acknowledged_at.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
This is OPTIONAL and never gates the shipment: a partner that skips it simply ships from the downloaded state via Fulfill Order. Idempotent — re-acknowledging is a no-op (acknowledged_at is preserved). An acknowledged order still appears in List Orders until it ships.
Path param: fulfillmentOrder — the FO id (from List Orders).
No request body.
Responses: 200 (acknowledged, returns the order); 422 (the order is completed or cancelled); 404 (the order is not at one of this partner's mapped warehouses, or it was dispatched to a different shipping provider — such orders are excluded from List Orders).
Auth: 3PL Integration Token (Bearer).
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not Found
Response Headers
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.