Fulfillment Manager API · orders

A page of the organization's backorder queue

GET /backorders

A page of the organization's backorder queue: the orders still waiting on stock — status open, awaiting-stock or partially-shipped with outstanding shortfalls — sorted oldest wait first, limit per page (1–200, 50 when omitted) from offset, with the queue's total.

Served from a per-SKU backorder index written with each order, so a page never loads the organization's order history. Each entry carries the per-SKU shortfall quantities, createdAt, waitingSince (when the current shortfall state began: the moment of the latest allocation run that left the order short, or the order's creation), and queuePosition — the order's 1-based rank, by creation sequence, among backordered orders shorted on any of the same SKUs. ?sku= narrows the list to orders short of that SKU; positions are still computed against the whole queue. Allocation policy (documented here on purpose): stock is granted strictly oldest-order-first by creation sequence per SKU — the earliest-created order short of a SKU is offered everything it still needs before the next order in line gets anything; there is no partial-fairness or pro-rata split across competing orders, and no priority rules. Appends nothing: a read of the backorder index.

Access

Requires orders:read.

How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.

AI agent tool

Agents call this as fulfillment_backorders (Fulfillment: Backorders), in the orders toolset. It only reads.

Connecting an agent: AI agents.

Example

curl
curl -X GET 'https://fulfillment.getmanifold.io/backorders?limit=50' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"
JavaScript (fetch)
const response = await fetch("https://fulfillment.getmanifold.io/backorders?limit=50", {
  method: "GET",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}` },
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();
Response · 200 · application/json
{
  "items": [
    {
      "orderId": "ord_01a15960-bec0-7fd1-8ae2-93a4b5c6d7e8",
      "number": "SO-01046",
      "reference": "PO-7810",
      "status": "awaiting-stock",
      "shortfalls": [
        {
          "sku": "BOWL-SALT-L",
          "quantity": 3
        }
      ],
      "createdAt": "2026-10-20T07:45:12.001Z",
      "waitingSince": "2026-10-20T07:45:12.001Z",
      "queuePosition": 1
    }
  ],
  "total": 1,
  "limit": 50,
  "offset": 0
}

The panel writes this call in other languages. It does not send it: Manifold's APIs do not take calls from a web page on another site, so run the call from your own code or terminal. The whole API as OpenAPI: fulfillment-manager.openapi.json. Base URL https://fulfillment.getmanifold.io.

Errors

Every refusal is a status and a JSON body whose _tag names it. A refused call changes nothing.

401

RefusalWhat it meansWhat to do
Unauthorized reason The token is missing, expired or not one Manifold issued.Get a fresh token and send the call again.
TokenAlreadyUsed tokenId A single-use app token was already spent.Mint a new token for this call.

402

RefusalWhat it meansWhat to do
SubscriptionRequired status The organization's subscription has lapsed, so writes are refused.An owner settles billing. Reads still work meanwhile.

403

RefusalWhat it meansWhat to do
TenantRequired userId The token names no organization.Choose the organization, then get a new token.
ScopeRequired required The token's roles do not grant the scope this call needs.Ask an owner or admin for a role that grants it.

409

RefusalWhat it meansWhat to do
MirroredFromSource source This area is fed by your source system until the organization goes live.Make the change in the source system, or go live first.

503

RefusalWhat it meansWhat to do
RequestLogUnavailable tokenId, reason The service could not record the request, so it did nothing.Try again shortly.

How refusals work everywhere: Errors.

Used in