Update a Transaction Route
Use this endpoint to update the details of a Transaction Route.
Path Parameters
The unique identifier of the Organization associated with the Ledger.
The unique identifier of the associated Ledger.
The unique identifier of the Transaction Route that you want to retrieve.
Body
Short text summarizing the purpose of the transaction. Used as an entry note for identification.
255A description for the Transaction Route.
250A list of Operation Route IDs that define the source and destination logic for the transaction. Important: A transaction route must include at least one operation route with type: "source" and at least one operation route with type: "destination".
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 resource was successfully created and the operation was completed as expected.
The unique identifier of the Transaction Route.
The unique identifier of the Organization.
The unique identifier of the Ledger.
Short text summarizing the purpose of the transaction. Used as an entry note for identification.
A description for the Transaction Route.
List of objects containing information about the Operation Routes from the Transaction Route.
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.

