Skip to main content
GET
Get accrual run

Authorizations

Authorization
string
header
required

JWT bearer token issued by the identity provider.

Path Parameters

id
string<uuid>
required

Accrual run identifier.

Example:

"550e8400-e29b-41d4-a716-446655440000"

Response

OK

businessDate
string
required

Business date the run was executed for (YYYY-MM-DD, UTC).

Example:

"2026-06-14"

correlationId
string
required

Correlation identifier linking the run to its journal lineage and downstream events. Not unique: several runs can share one.

Example:

"accrual-run-2026-05-31"

createdAt
string
required

Creation timestamp (RFC3339, UTC).

Example:

"2026-06-14T03:00:00Z"

id
string
required

Accrual run identifier (uuid).

Example:

"550e8400-e29b-41d4-a716-446655440000"

journalReferenceId
string
required

Journal reference (uuid) recording this run's posting lineage.

Example:

"550e8400-e29b-41d4-a716-446655440001"

postingStatus
string
required

State of the downstream ledger posting. "pending" means the ledger has not confirmed it, "posted" means it accepted it, "no_items" means the run recognized nothing so nothing was sent.

Example:

"pending"

status
string
required

Lifecycle status of the run.

Example:

"queued"

updatedAt
string
required

Last update timestamp (RFC3339, UTC).

Example:

"2026-06-14T03:05:00Z"

externalJournalReferenceId
string

Always omitted on a run: a run emits one posting per contract per competência per kind, so no single ledger transaction identifies it. The ledger's identifier is per posting — resolve one through GET /api/v1/journal-references with that posting's correlation identifier.