Replay committed webhooks events at-or-after since

GET /events

Replay committed webhooks events at-or-after since (a journal sequence number), oldest first: every subscription an app saved or let go.

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 integrations:read.

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://webhooks.getmanifold.io/events?since=0&limit=500' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://webhooks.getmanifold.io/events?since=0&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": "webhooks.subscription-saved",
    "eventId": "evt_01a158e5-f560-7d19-8b2c-4a7e1f0d3c58",
    "txId": "tx_01a158e5-f560-7e0a-a3d4-9b1c6e2f8a07",
    "tenantId": "org_01a15889-fa80-7d83-add6-41f282c51558",
    "sequence": 0,
    "occurredAt": "2026-10-20T11:00:00.000Z",
    "source": "webhooks",
    "version": 1,
    "actor": {
      "_tag": "app",
      "id": "app_01a158db-8198-7d68-bdb3-a6b194c0ce9e",
      "installationId": "ins_01a158dd-98c0-7c1e-9f42-3b7d2a1e6c05"
    },
    "correlationId": "req_01a158e5-f560-7f3b-9c11-2d8e5a4b6f90",
    "payload": {
      "subscriptionId": "whs_01a158d9-6a70-7aa9-a2e3-50b645a781d0",
      "appId": "app_01a158db-8198-7d68-bdb3-a6b194c0ce9e",
      "installationId": "ins_01a158dd-98c0-7c1e-9f42-3b7d2a1e6c05",
      "url": "https://hooks.tidewater-labels.example/manifold",
      "topics": [
        "order.created",
        "shipment.shipped"
      ]
    }
  }
]

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