Fulfillment Manager API · orders
What in the order book needs a person today — the home dashboard's fulfilment summary
GET /orders/attention
unfulfilled counts orders placed but not fully shipped (open, awaiting-stock, partially-shipped; drafts and cancellations are not work), awaitingStock the ones among them waiting on stock, and shipments their parcels by stage: pending (to pick), picked (to pack), packed (to ship). awaitingPayment is the prepaid orders holding a packed parcel until the balance is paid, and refundsOwed the orders whose customer has paid more than the order now totals (an edit took value off a paid order) — each with how many, the sum per currency (never across currencies), and the five longest waiting. Read from the order projection as it stands; read-only.
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_get_orders_attention (Fulfillment: Get orders attention), in the orders toolset. It only reads.
Connecting an agent: AI agents.
Example
curl -X GET 'https://fulfillment.getmanifold.io/orders/attention' \
-H "Authorization: Bearer $MANIFOLD_TOKEN"const response = await fetch("https://fulfillment.getmanifold.io/orders/attention", {
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();{
"unfulfilled": 5,
"awaitingStock": 1,
"shipments": {
"pending": 4,
"picked": 0,
"packed": 1
},
"awaitingPayment": {
"orders": 0,
"amounts": [],
"oldest": []
},
"refundsOwed": {
"orders": 0,
"amounts": [],
"oldest": []
}
}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
| Refusal | What it means | What 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
| Refusal | What it means | What to do |
|---|---|---|
SubscriptionRequired status | The organization's subscription has lapsed, so writes are refused. | An owner settles billing. Reads still work meanwhile. |
403
| Refusal | What it means | What 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
| Refusal | What it means | What 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
| Refusal | What it means | What 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
- Read the dashboard and tidy it, step 2: What the order book needs