Purchasing Manager API · events
Replay committed purchasing events at-or-after since
GET /events
Replay committed purchasing events at-or-after since (a journal sequence number), oldest first.
One response is a page: limit defaults to 500 and is capped at 5000 (an over-cap request is clamped). Pages are sequence-ordered and the boundary is stable — repeat with since=<last event's sequence + 1> until a page comes back smaller than limit to replay the journal exactly once. upTo (inclusive) ends the replay at a sequence instead of the journal's head — with GET /events/head it replays the journal as it stood at a moment. Appends nothing: a read of facts already journalled.
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
No agent tool. The journal replay a consumer pages through to build its projection; agents read the projections the list and get tools serve, and the audit trail (audit_trail) for history.
Connecting an agent: AI agents.
Example
curl -X GET 'https://purchasing.getmanifold.io/events?since=2&limit=500' \
-H "Authorization: Bearer $MANIFOLD_TOKEN"const response = await fetch("https://purchasing.getmanifold.io/events?since=2&limit=500", {
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();[
{
"_tag": "purchasing.po-authorised",
"eventId": "evt_01a12465-9700-7e2b-b08b-c83673208051",
"txId": "tx_01a12465-9700-7e2b-b08b-c83673208052",
"tenantId": "org_01a1586e-f9f6-7a8b-9c7d-6e5f4a3b2c1d",
"sequence": 2,
"occurredAt": "2026-09-22T01:20:00.000Z",
"source": "purchasing-manager",
"version": 1,
"actor": {
"_tag": "user",
"id": "usr_01a12e7b-6080-7a3c-a1fc-94dbc33aeadb"
},
"correlationId": "req_01a12465-96f0-7a10-8e1d-4c2b9a7f3e60",
"payload": {
"poId": "po_01a15876-6c9e-7b3a-8c4d-9e0f1a2b3c4d",
"document": {
"number": "PO-00001",
"reference": "PO-WIDGET-BLUE",
"currency": "AUD",
"supplier": {
"companyId": "cmp_01a15884-6399-7e5f-8a6b-1c2d3e4f5a6b",
"name": "Northwind Components"
},
"lines": [
{
"sku": "WIDGET-BLUE",
"name": "Blue widget, 40mm",
"quantity": 40,
"unitCostCents": 1250
}
],
"totalCents": 50000
}
}
}
]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.