Replay committed reporting events at-or-after since

GET /events

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

The journal holds the report library's changes (reporting.report-saved) and the dashboard cards people dismiss and restore (reporting.widget-dismissed, reporting.widgets-restored); the read model the reports run over is folded from other services' journals and never lands here. limit caps a page (default 500, capped at 5000); repeat with since=<last sequence + 1> until a short page. 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 reports: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://reporting.getmanifold.io/events?since=2&limit=500' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://reporting.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();

Response · 200 · application/json

[
  {
    "_tag": "reporting.report-saved",
    "eventId": "evt_01a13d49-a900-7c3e-9ed6-6bd67d1d0ecf",
    "txId": "tx_01a13d49-a900-7c3e-9ed6-6bd67d1d0ed0",
    "tenantId": "org_01a1586e-f9f6-7a8b-9c7d-6e5f4a3b2c1d",
    "sequence": 2,
    "occurredAt": "2026-10-20T08:41:12.000Z",
    "source": "reporting-manager",
    "version": 1,
    "actor": {
      "_tag": "user",
      "id": "usr_01a12e7b-6080-7a3c-a1fc-94dbc33aeadb"
    },
    "correlationId": "req_01a13d49-a8f0-7a51-8e1d-4c2b9a7f3e61",
    "payload": {
      "reportId": "rpt_01a1586d-1d4c-7444-8444-444444444444",
      "name": "Units by SKU, last 30 days",
      "definition": {
        "entity": "stockMovement",
        "hops": [
          "sku"
        ],
        "groupBy": [
          {
            "field": "sku"
          }
        ],
        "measures": [
          "quantity"
        ],
        "period": {
          "_tag": "preset",
          "preset": "30d"
        },
        "filters": [],
        "derived": [],
        "limit": 100
      }
    }
  }
]

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

Build, save and run a report, step 9: The journal shows exactly two saves