Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
The type of media of the resource. Must be <code>application/json</code>.
A unique identifier used to trace and track each request.
A unique key that ensures transaction idempotency. If not provided, the system automatically generates a hash based on the transaction data.
The time-to-live for the key, defined in seconds.
Path Parameters
The unique identifier of the Organization associated with the Ledger.
The unique identifier of the associated Ledger.
Body
A description for the transaction.
An object containing information about the transaction that will be sent.
An object containing key-value pairs to add as metadata, where the field <code>name</code> is the key and the field <code>value</code> is the value. For example, to add a Cost Center, use 'costCenter': 'BR_11101997'.
Response
Indicates that the resource was successfully created and the operation was completed as expected.
The unique identifier of the transaction.
The unique identifier of the Organization.
The unique identifier of the Ledger.
Description of the transaction.
The unique identifier of the template if the transaction is templated.
The transaction status (pending, completed, reversed).
The sent amount.
The number of decimal points used to display the amount.
The name of the asset used in the operation.
The name of the group used to categorize the operations of a transaction under the same group.
The list of accounts used as source.
The list of accounts used as destination.
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 <code>name</code> is the key and the field <code>value</code> is the value. For example, to add a Cost Center, use 'costCenter': 'BR_11101997'.