Update Journal Entry

post/extensions/roboledger/{graph_id}/operations/update-journal-entry

Update a draft journal entry. Posted entries are immutable and must be corrected via create-event-block(event_type='journal_entry_reversed'). If line_items is provided, existing line items are replaced atomically, the new set must balance, and a line on a retired (is_active=false) account is refused.

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.

Authentication

Authenticate in any one of these ways — not all of them:

API key in the X-API-Key header.
Bearer token in the Authorization header.

Path parameters

Name	Type	Description
`graph_id`required	string	Graph Id

Header parameters

Name	Type	Description
`Idempotency-Key`optional	string	Idempotency-Key

Request body

Required, application/json.

Field Type Description

entry_idrequired

string

The draft entry to update.

posting_dateoptional

string (date)

New posting date.

memooptional

string

New entry-level memo.

typeoptional

string

New entry type. `closing` should normally only be set by close-period.

One of: standard, adjusting, closing, reversing

line_itemsoptional

JournalEntryLineItemInput[]

Replacement line items. Whole-list replacement (not patch). The new set must still balance (total_debit == total_credit). Omit to leave existing lines untouched.

JournalEntryLineItemInput fields

Field	Type	Description
`element_id`required	string	Element ULID identifying the account to post to.
`debit_amount`optional	integer	Debit amount in cents. Must be 0 if `credit_amount` > 0. Default: `0`
`credit_amount`optional	integer	Credit amount in cents. Must be 0 if `debit_amount` > 0. Default: `0`
`description`optional	string	Per-line memo (overrides the entry-level memo on this line).
`metadata`optional	object	Optional per-line metadata stamped on ``LineItem.metadata_``. Used to carry source-system fields the standard columns don't cover — e.g. an external flow-tag code that drives rollforward attribution (``transaction_description_code``), an external memo, or a cost-center hint. Pass-through is non-validating; the renderer / filter engine reads keys it knows about and ignores the rest. ``None`` is normalized to ``{}`` at persist time.

Example request

curl

curl -X POST "https://api.robosystems.ai/extensions/roboledger/{graph_id}/operations/update-journal-entry" \
  -H "X-API-Key: $ROBOSYSTEMS_API_KEY" \
  -H "Idempotency-Key: <Idempotency-Key>" \
  -H "Content-Type: application/json" \
  -d '{
  "entry_id": "ent_01HVF8T0M2YTAY3BBNRH0V0",
  "memo": "Corrected vendor reference"
}'

Responses

200 Successful Response

Field Type Description

operationrequired

string

Kebab-case operation name

operationIdrequired

string

op_-prefixed ULID for audit and SSE correlation

statusrequired

string

Operation lifecycle state

One of: completed, pending, failed

resultoptional

JournalEntryResponse

Command-specific result payload

JournalEntryResponse fields

Field Type Description

idrequired string

transaction_idoptional string

typerequired string

statusrequired string

posting_daterequired string (date)

memooptional string

provenanceoptional string

reversal_ofoptional string

posted_atoptional string (date-time)

line_itemsrequired

JournalEntryLineItemResponse[]

One line in a journal entry response.

JournalEntryLineItemResponse fields

Field	Type	Description
`id`required	string
`element_id`required	string
`debit_amount`required	integer
`credit_amount`required	integer
`description`optional	string
`line_order`required	integer

total_debitrequired integer

total_creditrequired integer

atrequired

string

ISO-8601 UTC timestamp

createdByoptional

string

User ID that initiated the operation (null for legacy callers)

idempotentReplayoptional

boolean

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

Default: false

Status	Meaning
400	Invalid request
401	Authentication required
403	Access denied
404	Resource not found
409	Idempotency-Key conflict — key reused with different body
422	Validation error
429	Rate limit exceeded
500	Internal server error