Replay committed events at-or-after since (a journal sequence number), oldest first

GET /events

Use to catch up before subscribing to /events/stream. 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 stock:read or products:read or catalogs:read or locations: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

curl -X GET 'https://inventory.getmanifold.io/events?since=1042&limit=500' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://inventory.getmanifold.io/events?since=1042&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();

Response · 200 · application/json

[
  {
    "_tag": "inventory.stock-dispatched",
    "eventId": "evt_01a1615a-c0e0-7d38-a94d-ee5249f39be3",
    "txId": "tx_01a1615a-c0e0-7de2-b618-5b6075c9f4c7",
    "tenantId": "org_019cadd3-7f48-7813-b601-1d0e5ec31353",
    "sequence": 1042,
    "occurredAt": "2026-10-22T02:05:00.000Z",
    "source": "inventory-manager",
    "version": 1,
    "actor": {
      "_tag": "user",
      "id": "usr_019cadd3-7fc0-792b-bb42-1992ef490f3b"
    },
    "correlationId": "req_01a1615a-c0e0-756f-be6c-4dc5e8f50d4d",
    "payload": {
      "sku": "WIDGET-BLUE",
      "locationId": "loc_019cadd3-8330-7e12-aa44-2cd5f05da74a",
      "quantity": 2,
      "orderId": "ord_01a1612f-7ea8-705d-b799-e8d57826848d",
      "reference": "dsp_309cca80-6f93-1b13-35a3-a6c100d3dd4d"
    }
  }
]

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: inventory-manager.openapi.json. Base URL https://inventory.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.