v1
latestOpenAPI 3.1.02026-07-263644911022.4 KBCreate a Transaction using JSON
Use this endpoint to create a transaction using JSON.
Transaction lifecycle: the transaction is persisted with an initial status of CREATED and is promoted to APPROVED asynchronously after balance processing completes. The CREATED state is transient; clients should treat it as in-progress and not assume final settlement until the status reaches APPROVED.
Path parameters
The unique identifier of the Organization associated with the Ledger.
The unique identifier of the associated Ledger.
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>
A unique key that ensures transaction idempotency. If not provided, the system automatically generates a SHA-256 hash based on the request body. Keys are scoped per organization and ledger.
Always validate the X-Idempotency-Replayed response header to distinguish new transactions from cached replays.
See Retries and idempotency for best practices.
The time-to-live for the idempotency key, defined in seconds. Defaults to 300 seconds (5 minutes) if not provided. Only the TTL from the first request is used; changing it on retries has no effect.
See Retries and idempotency for details.
Request body
Response
Indicates that the resource was successfully created and the operation was completed as expected.
The response includes the X-Idempotency-Replayed header.
If the value is false, the transaction was just processed. If the value is true, the response is a replay of a previously processed request.
See Retries and idempotency for more details.