Purchasing Manager API · pos
When each open purchase order will really arrive
GET /arrivals
When each open purchase order will really arrive: a projected day with a band (earliestOn–latestOn) and a confidence, standing on (basis) an inbound shipment's ETA and its carrier's record of meeting ETAs, else the expected day moved by the supplier's usual lateness, else the day placed plus the supplier's learned lead time — and a risk: overdue, at-risk (the projection or its late end falls after the expected day), on-track or unknown.
Soonest first. What the dashboard's arriving and overdue deliveries read.
Access
Requires purchasing:read or receiving:read.
Any one of these scopes is enough.
How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.
AI agent tool
Agents call this as purchasing_list_arrivals (Purchasing: List arrivals), in the reporting toolset. It only reads.
Connecting an agent: AI agents.
Example
curl -X GET 'https://purchasing.getmanifold.io/arrivals' \
-H "Authorization: Bearer $MANIFOLD_TOKEN"const response = await fetch("https://purchasing.getmanifold.io/arrivals", {
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();{
"asOf": "2026-10-29",
"items": [
{
"poId": "po_01a1340f-9980-7c41-9d37-d97a5cec069b",
"number": "PO-00002",
"supplier": "Northwind Components",
"supplierId": "cmp_01a15884-6399-7e5f-8a6b-1c2d3e4f5a6b",
"status": "authorised",
"expectedOn": "2026-11-04",
"projectedOn": "2026-11-04",
"earliestOn": "2026-11-02",
"latestOn": "2026-11-07",
"basis": "expected",
"confidence": "high",
"risk": "at-risk",
"sample": 12,
"outstanding": 30
}
]
}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: purchasing-manager.openapi.json. Base URL https://purchasing.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.