Bulk Sync Fulfillment Orders from Provider
POST/api/fulfillment-orders/bulk-sync-from-provider
Update tracking for many fulfillment orders at once by polling each one's registered provider order. Accepts an explicit ids selection, or apply_to_all=true — in which case the entire filtered set is resolved server-side from the request query string's current filter[...] / filter_groups parameters (the same filters as the fulfillment orders list endpoint). There is no body filters parameter.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
This endpoint is asynchronous: it dispatches a background job and returns immediately with a tracked_job_log_id that can be used to monitor progress. Fulfillment orders with no registered provider order yet are skipped by the job rather than rejected here.
Body fields:
ids(array of integers, required unlessapply_to_allis true) — fulfillment order IDs to sync.apply_to_all(optional, boolean) — sync every fulfillment order matching the current query-string filters.
Authentication: Requires Bearer token.
Required permission: fulfillment_orders.submit (Fulfillment Orders → Submit & sync) and fulfillment_orders.index (Fulfillment Orders → View). A token also needs its orders scope; the owner needs these role permissions.
Request
Responses
- 200
- 401
- 403
- 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
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.