Skip to main content
PATCH
Update an Operation

Headers

Content-Type
string

The type of media of the resource. Recommended value is application/json.

X-Request-Id
string<uuid>

A unique identifier used to trace and track each request.

Authorization
string

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

organization_id
string<uuid>
required

The unique identifier of the Organization associated with the Ledger.

ledger_id
string<uuid>
required

The unique identifier of the associated Ledger.

operation_id
string<uuid>
required

The unique identifier of the operation that you want to retrieve.

transaction_id
string<uuid>
required

The unique identifier of the transaction you want to retrieve.

Body

application/json
description
string

The description for the operation.

Maximum string length: 256
metadata
object

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.

Response

Indicates that the request was successful and the response contains the expected data.

id
string<uuid>

The unique identifier of the Operation.

transactionId
string<uuid>

The unique identifier of the Transaction.

organizationId
string<uuid>

The unique identifier of the Organization.

ledgerId
string<uuid>

The unique identifier of the Ledger.

accountId
string<uuid>

The unique identifier of the Account.

accountAlias
string

The alias for the account used in the operation.

balanceId
string

The unique identifier of the Balance.

balanceKey
string

The unique key that identifies the Balance.

description
string

Description of the transaction.

type
enum<string>

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.

Available options:
CREDIT,
DEBIT,
ON_HOLD,
RELEASE,
OVERDRAFT,
BLOCK,
UNBLOCK
assetCode
string

The name of the asset used in the operation.

chartOfAccounts
string

The name of the Chart-of-Accounts that the operation belongs to.

route
string
deprecated

Deprecated. Use routeId instead. Will be removed in the next major version. The unique ID of the operation route for this transaction leg.

routeId
string<uuid>

The unique identifier of the operation route associated with this operation. Companion overdraft operations inherit this value from the primary operation that triggered them.

routeCode
string

A human-readable code for the operation route, useful for audit trail and traceability.

Maximum string length: 100
routeDescription
string

The description of the operation route associated with this operation.

direction
enum<string>

The direction of the operation in double-entry accounting.

Available options:
debit,
credit
amount
object

An object containing information about the amount used in the operation.

balance
object

An object containing information about the balance before the operation.

balanceAfter
object

An object containing information about the balance after the operation.

status
object

The transaction status (pending, completed, reversed).

balanceAffected
boolean

If true, indicates that the operation affected the account balance.

createdAt
string<date-time>

Timestamp of creation (UTC).

updatedAt
string<date-time>

Timestamp of last update (UTC).

deletedAt
string<date-time> | null

Timestamp of soft deletion, if applicable (UTC).

metadata
object

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.