Use this endpoint to create a transaction using a DSL file you have previously created.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
El token de autorización. Este encabezado es requerido si su entorno tiene el Access Manager habilitado.
El tipo de medio del recurso. Debe ser application/json.
Un identificador único utilizado para rastrear y seguir cada solicitud.
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.
The unique identifier of the Organization associated with the Ledger.
The unique identifier of the associated Ledger.
The .gold file you have created with the transaction information.
Indica que el recurso fue creado exitosamente y la operación se completó como se esperaba.
The unique identifier of the transaction.
The unique identifier of the Organization.
El identificador único del Ledger.
Description of the transaction.
Specifies the Transaction Route associated with the transaction.
The transaction status (pending, completed, reversed).
The sent amount.
The name of the asset used in the operation.
The name of the chart-of-accounts 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 name is the key and the field value is the value. For example, to add a Cost Center, use 'costCenter': 'BR_11101997'.