Update an Operation
Use this endpoint to update the details of an Operation.
Headers
The type of media of the resource. Recommended value is application/json.
A unique identifier used to trace and track each request.
Bearer JWT token for authentication.
Required when PLUGIN_AUTH_ENABLED=true (enforced in multi-tenant deployments).
Optional in default OSS single-tenant mode.
Format: Bearer <token>
Path Parameters
The unique identifier of the Organization associated with the Ledger.
The unique identifier of the associated Ledger.
The unique identifier of the operation that you want to retrieve.
The unique identifier of the transaction you want to retrieve.
Body
The description for the operation.
256An object containing key-value pairs to add as metadata, where the field name is the key and the field value is the value. For example, to add a Cost Center, use 'costCenter': 'BR_11101997'.
Constraints: keys must be at most 100 characters; string values at most 2000 characters. Nested objects are not allowed (values must be string, number, or boolean), the structure may not exceed a maximum depth of 10, and a maximum of 100 keys is permitted.
Response
Indicates that the request was successful and the response contains the expected data.
The unique identifier of the Operation.
The unique identifier of the Transaction.
The unique identifier of the Organization.
The unique identifier of the Ledger.
The unique identifier of the Account.
The alias for the account used in the operation.
The unique identifier of the Balance.
The unique key that identifies the Balance.
Description of the transaction.
The type of the operation. OVERDRAFT identifies system-generated companion operations on the internal "overdraft" balance — direction then carries the lifecycle semantics (debit for a draw, credit for a repayment). BLOCK and UNBLOCK identify operations produced by the block/unblock transaction endpoints; direction still carries the debit/credit semantics.
CREDIT, DEBIT, ON_HOLD, RELEASE, OVERDRAFT, BLOCK, UNBLOCK The name of the asset used in the operation.
The name of the Chart-of-Accounts that the operation belongs to.
Deprecated. Use routeId instead. Will be removed in the next major version. The unique ID of the operation route for this transaction leg.
The unique identifier of the operation route associated with this operation. Companion overdraft operations inherit this value from the primary operation that triggered them.
A human-readable code for the operation route, useful for audit trail and traceability.
100The description of the operation route associated with this operation.
The direction of the operation in double-entry accounting.
debit, credit An object containing information about the amount used in the operation.
An object containing information about the balance before the operation.
An object containing information about the balance after the operation.
The transaction status (pending, completed, reversed).
If true, indicates that the operation affected the account balance.
Timestamp of creation (UTC).
Timestamp of last update (UTC).
Timestamp of soft deletion, if applicable (UTC).
An object containing key-value pairs to add as metadata, where the field name is the key and the field value is the value. For example, to add a Cost Center, use 'costCenter': 'BR_11101997'.
Constraints: keys must be at most 100 characters; string values at most 2000 characters. Nested objects are not allowed (values must be string, number, or boolean), the structure may not exceed a maximum depth of 10, and a maximum of 100 keys is permitted.

