RoboLedger: Ledger & Events

Propose Consolidation Entries

Draft a month's consolidating entries in the group's consolidation entity: what preview-consolidation-entries computes, written as drafts that the consolidation entity's close posts. Proposing the month again replaces the drafts it wrote before, so it can be run after any member's books change; a person's own entries are never touched. Lines that eliminate a cash flow carry the row they offset. A residual or a disagreement is returned beside the drafts, never plugged; a month the consolidation entity has closed is left as posted.

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/propose-consolidation-entries

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/propose-consolidation-entries
  • 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

The month, as YYYY-MM.

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.