Transactions
Create new transaction
Post a transaction in your Blnk Ledger.
POST
If you’re using the auto-provisioned
Enterprise Core instance included with your Production License deployment, set the base URL to: https://ENTERPRISE_PUBLIC_URL/core.If you’re connecting to a different Core instance, use the publicly accessible base URL for that instance instead.Authorization
If set, the API uses an API key for authentication. Include the following header in your requests:X-blnk-key: <api-key>.
Replace <api-key> with your secret API key. Ensure the key is kept secure and not exposed in public repositories or client-side code.
See also: Scoped API keys and Secure your Blnk server.
Body
The transaction amount in its smallest unit (recommended). Include the corresponding
precision value. See Precision.The transaction amount as a float. Blnk multiplies
amount by precision to store precise_amount. The amount field supports up to 15 digits; use precise_amount for larger values. See also: Precision.The currency of the transaction amount is in.
The unique transaction reference number for the transaction.
The unique id of the balance sending the amount.
@ prefix indicates that the balance is an internal balance.The unique id of the balance receiving the amount.
@ prefix indicates that the balance is an internal balance.Narration of the transaction.
Indicates the date and time of a scheduled transaction.Always format the date input as ‘YYYY-MM-DDTHH:MM:SS+00:00’ (e.g., 2024-04-22T15:28:03+00:00), where
+00:00 specifies the timezone. It is UTC by default.Specifies whether the transaction should proceed even if the source’s balance is insufficient. If enabled and the source has less than the required amount, the balance will become negative. See also: Overdrafts
Specifies that the transaction should be held until certain conditions are met. See also: Create inflight.
Specifies the date and time when an inflight transaction should expire. Once expired, the transaction is voided and the amount is rolled back.Always format the date input as ‘YYYY-MM-DDTHH:MM:SS+00:00’ (e.g., 2024-04-22T15:28:03+00:00), where
+00:00 specifies the timezone. It is UTC by default.When
inflight is true, the date and time when Blnk should automatically commit the inflight transaction (same ledger outcome as Update Inflight with commit). See Schedule inflight commits.Always format the date input as ‘YYYY-MM-DDTHH:MM:SS+00:00’ (e.g., 2024-04-22T15:28:03+00:00), where +00:00 specifies the timezone. It is UTC by default.Specifies the actual date the transaction occurred. Learn more: Backdated transactions.
When
true, it bypasses the default transaction queuing system and processes transactions directly. See also: Skip transaction queue.Controls how Blnk processes split transactions when you use
sources or destinations. When false (default), Blnk applies each leg that can succeed and rejects legs that fail. When true, every leg succeeds together or the entire split fails with no partial application. See Multiple sources and Multiple destinations.Additional metadata of the transaction.
Response
All parameters from the request body also mean the same in the corresponding response JSON.
The amount stored in the ledger in its smallest unit. When you pass
amount, Blnk computes this as amount x precision. See Precision.Unique id of the transaction.
The transaction ID of the parent transaction. A parent transaction is one that impacts the creation of a new transaction, such as an inflight transaction, a scheduled transaction, or similar.For instance, refunding a sample transaction A creates a new transaction B; therefore A is the parent transaction of B.
The status of the transaction. See the following: Transaction statuses.
Per-row SHA-256 fingerprint of the transaction’s core details. The optional global hash chain is separate and not returned in API responses. Learn more: Transaction hashing
Indicates the date & time the transaction was created.
Additional metadata of the transaction.