Bulk Request Fulfillment Tracking Updates
PUT/api/sales-order-fulfillments/tracking-updates
Request fresh tracking information from shipping providers for the selected fulfillments.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body:
ids(optional) — array of fulfillment IDs or a comma-separated string ("4821,4977"). Unknown IDs are ignored.
Only fulfillments of type starshipit, shipstation, or fba that are not yet in fulfilled status are processed; all others are skipped silently.
May run asynchronously — when more than 10 fulfillments match for a provider, the sync is queued as a background job and the response says so; smaller selections are polled inline against the provider before responding.
Side effects: tracking numbers and URLs are written back, and a shipment found shipped/delivered at the provider transitions to fulfilled — which records inventory movements, consumes cost layers, and submits the fulfillment to the sales channel.
Errors: 400 when the required shipping-provider integration is not connected, or when the provider API returns an error.
Requires the orders:write token scope.
Request
Responses
- 200
- 400
- 401
- 403
- 422
- 429
OK
Response Headers
Bad Request
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.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.