Replication-slot health for accounting's read replica

GET /replica/status

Replication-slot health for accounting's read replica, one entry per configured source journal (inventory, purchasing, fulfillment).

Each entry reports the slot name, whether a walsender is attached (active), and lagBytes — the WAL the source database is retaining for this consumer, measured on the source as pg_wal_lsn_diff(pg_current_wal_lsn(), restart_lsn). stalled is true when the slot is inactive, missing, unreachable, or lagging past warnBytes (REPLICA_LAG_WARN_BYTES, default 256 MiB). This matters because a stalled slot retains WAL on the source until its disk fills — check here (or the periodic accounting.replica log line) before that happens. Liveness is deliberately separate: /healthz stays 200 while this payload carries the warning. Empty slots means accounting is running without a replica (HTTP-source fallback). Break-glass for a permanently dead consumer: SELECT pg_drop_replication_slot('<slot>') on the source, then re-establish the subscription. Appends nothing: a read of facts already journalled.

Access

Requires activity:read.

How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.

AI agent tool

No agent tool. Replication lag between the journals and this service's read model: an operator's health signal, not merchant data.

Connecting an agent: AI agents.

Example

curl

curl -X GET 'https://accounting.getmanifold.io/replica/status' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://accounting.getmanifold.io/replica/status", {
  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

{
  "warnBytes": 268435456,
  "slots": [
    {
      "source": "inventory",
      "slot": "accounting_inventory_events_sub",
      "active": true,
      "lagBytes": 4096,
      "stalled": false
    },
    {
      "source": "purchasing",
      "slot": "accounting_purchasing_events_sub",
      "active": true,
      "lagBytes": 0,
      "stalled": false
    },
    {
      "source": "fulfillment",
      "slot": "accounting_fulfillment_events_sub",
      "active": true,
      "lagBytes": 12288,
      "stalled": false
    }
  ]
}

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

Procure to pay, step 11: Check the replica is keeping up