Transactions
Multiple Sources
Move money to one balance from two or more balances.
POST
Documentation Index
Fetch the complete documentation index at: https://docs.blnkfinance.com/llms.txt
Use this file to discover all available pages before exploring further.
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: Secure your Blnk server
Body
Important tip: To apply multiple sources, Blnk uses the
sources array instead of the conventional source parameter in Record transaction.The transaction amount.
The transaction amount in its smallest unit. Use this instead of
amount when working with values that have more than 15 digits to avoid rounding errors. You must provide the corresponding precision value. See Transaction precision for more details.The currency of the transaction amount is in.
The unique transaction reference number for the transaction. If empty, Blnk auto-creates one.
Lists the sources for the transaction. Each source includes:
The balance receiving the amount.
@ prefix indicates that the balance is an internal balance.Indicates the date and time of a scheduled transaction, e.g.,
"2024-02-20 05:28:03".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: Inflight transactions.
Specifies the date and time when an inflight transaction should expire. Once expired, the transaction is voided and the amount is rolled back.
When
inflight is true, the date and time when Blnk should automatically commit the inflight transaction. See Schedule inflight commits.Defines the conversion rate to be applied when the transaction involves balances in different currencies. See also: Applying rates.
Additional metadata of the transaction.
Response
All parameters from the request body also mean the same in the corresponding response JSON.
This is computed by
amount x precision. Learn why this is important: Why use precisionUnique 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.
SHA-256 hash of the transaction details. Learn more: Transaction hashingIndicates the date & time the transaction was created.
Additional metadata of the transaction.