RoboLedger: Ledger & Events

Refresh Reconciliations

Run every reconciliation that applies at a period end and record each result on its block. A ledger synced from QuickBooks is compared with QuickBooks' own trial balance, on one block for the whole ledger. Each asset account a schedule carries a balance on is compared with what its schedules say it holds, on a block of its own. Each account with a statement covering the period (record-statement-balance; the latest within its statement cycle) is compared with that balance. A block reconciles for the period when its difference is within its materiality. Running it again replaces the period's comparison, so the answer is always as of the last run. A block is created the first time its check applies, and from then on the period's close waits on it until set-reconciliation-policy releases it. The one exception is an account block whose first comparison does not tie: it is created without holding the close, so a difference found on first contact is reported and becomes a close requirement only when you turn it on. Returns every reconciliation's standing for the period. Use preview-reconciliations to see a comparison without recording it.

Idempotency: supply an Idempotency-Key header to make safe retries; replays within 24 hours return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.

post/extensions/roboledger/{graph_id}/operations/refresh-reconciliations

Request

  • Base URL: https://api.robosystems.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.robosystems.ai/extensions/roboledger/{graph_id}/operations/refresh-reconciliations
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Path parameters

graph_idstring required

Headers

Idempotency-Keystring nullable

Request body

periodstring required

Period to reconcile at its last day, as YYYY-MM.

entity_idstring nullable

The entity whose books to reconcile, by id. Omit for the group parent. Each entity's reconciliations, and the close they hold, are its own.

Example request

{
  "period": "2026-08"
}

Response

Successful Response

operationstring required

Kebab-case operation name

operationIdstring required

op_-prefixed ULID for audit and SSE correlation

status'completed' | 'pending' | 'failed' required

Operation lifecycle state

atstring required

ISO-8601 UTC timestamp

createdBystring nullable

User ID that initiated the operation

idempotentReplayboolean

True when this envelope came from the idempotency cache — the underlying command did not execute again. False on fresh executions.

Changes

No recorded changes to this operation across all 1 revision of this API.