Create an Operation Route
Use this endpoint to create an Operation Route.
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.
Body
Short text summarizing the purpose of the operation. Used as an entry note for identification.
255The type of the Operation Route. Use bidirectional when the route can operate in both directions.
source, destination, bidirectional Defines the rule for selecting the account that will participate in the operation (source or destination).
An external reference used to identify the operation route. Deprecated: use rubric codes inside accountingEntries instead.
100Detailed description of the Operation Route purpose and usage.
250An 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.
Accounting entries grouped by transaction action type. Each action maps to a pair of debit and credit rubrics.
Response
Indicates that the resource was successfully created and the operation was completed as expected.
The unique identifier of the Operation Route.
The unique identifier of the Organization.
The unique identifier of the Ledger.
Short text summarizing the purpose of the operation. Used as an entry note for identification.
An external reference used to identify the operation route. Deprecated: use rubric codes inside accountingEntries instead.
100Detailed description of the Operation Route purpose and usage.
The type of the Operation Route. Use bidirectional when the route can operate in both directions.
source, destination, bidirectional Accounting entries grouped by transaction action type. Each action maps to a pair of debit and credit rubrics.
Defines the rule for selecting the account that will participate in the operation (debit or credit).
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.

