List Active Fulfillment Orders (Dispatch Feed, capped)
GET/api/fulfillment-orders
Cross-order dispatch board feed: every ACTIVE fulfillment order across all sales orders (excludes closed and cancelled), with salesOrder (for sales_order_number), warehouse, and lines eager-loaded. The frontend groups these into Kanban columns by request_status / status (Awaiting dispatch → Submitting → Submitted/Accepted → In progress → Needs attention).
orders:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Lazy-load per lifecycle: pass lifecycle (manual|pickup|push|pull|channel) to load just that tab's lifecycle; the cap (most recent 500) then applies per lifecycle. Omit for all lifecycles. Pickup is request-status-driven (awaiting_pickup / picked_up) — an FO with a pickup fulfillment but no pickup method still lands under pickup, not its warehouse carrier. Use Dispatch Board — Lifecycle Counts for the tab badges.
Authenticate with a Personal Access Token.
Card detail fields: each FO also returns sales_order_date, customer_name, sales_channel_name, and total_quantity (sum of line quantities). packing_slip_printed_at is included too (null until printed).
Request
Responses
- 200
- 401
- 403
- 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.
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.