> ## 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.
# Bulk Transactions
> Handle bulk transactions in your Blnk Ledger.
export const CtaCallout = props => {
const {title, buttonLabel, href, trackingEvent, buttonTarget, rel = "noopener noreferrer", children} = props;
const handleCtaClick = () => {
if (typeof window === "undefined" || !trackingEvent) {
return;
}
try {
window.dispatchEvent(new CustomEvent("blnk:docs-cta", {
detail: {
name: trackingEvent,
href
}
}));
} catch {}
try {
window.posthog?.capture?.(trackingEvent, {
href
});
} catch {}
const gaPayload = {
cta_href: href
};
try {
window.gtag?.("event", trackingEvent, gaPayload);
} catch {}
try {
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
event: trackingEvent,
...gaPayload
});
} catch {}
};
const isExternal = typeof href === "string" && (/^https?:\/\//i).test(href);
const target = buttonTarget ?? (isExternal ? "_blank" : undefined);
const linkRel = isExternal ? rel : undefined;
return ;
};
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: `.
Replace `` 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](/api-keys/overview) and [Secure your Blnk server](/advanced/secure-blnk).
### Body
When `true`, either all transactions succeed or all fail. When `false`, transactions are processed independently.
When `true`, transactions are created in `INFLIGHT` status and require a separate commit. When `false`, transactions are applied immediately.
When `true`, processing happens in the background and results are delivered via webhook. When `false` or not provided, processing happens synchronously and results are returned in the response.
When `true`, transactions bypass the queue and are processed inline in the request. Duplicate-reference handling differs from the default queued path. See [Duplicate references](/transactions/bulk-transactions#duplicate-references).
An array of transaction objects. Max number of transactions allowed is 10,000.
```json Sample transaction object theme={"system"}
{
"precise_amount": 35890,
"precision": 100,
"reference": "unique_reference_1",
"description": "Transaction description",
"currency": "USD",
"source": "@source_account",
"destination": "@destination_account",
"allow_overdraft": true
}
```
### Response
Identifier for the bulk batch. Use this value as `parent_transaction` when [searching for child transactions](/transactions/bulk-transactions#retrieving-transactions-in-a-batch), or when [committing or voiding](/transactions/bulk-transactions#commit-or-void-bulk-inflight) an inflight batch.
When `run_async` is `false`, `applied` means the bulk request was accepted. With default queueing (`skip_queue: false`), children are processed asynchronously - `applied` does not mean every child is already `APPLIED` on balances. With `skip_queue: true`, children are processed inline before the response returns. Value is `inflight` when `inflight: true`. When `run_async` is `true`, value is `processing`.
Number of transactions in the request. Present on successful synchronous responses. On the default queued path, this reflects items submitted, not necessarily rows created - see [Duplicate references](/transactions/bulk-transactions#duplicate-references).
Human-readable status message. Included on the immediate response when `run_async` is `true` (for example, confirming that background processing started).
```json 200 theme={"system"}
{
"batch_id": "bulk_c62f200b-905f-4983-a349-cadd279234aa",
"status": "applied",
"transaction_count": 4
}
```
```json 400 theme={"system"}
{
"error": "transactions cannot be empty",
"error_detail": {
"code": "TXN_BULK_EMPTY",
"message": "transactions cannot be empty"
}
}
```
```json 400 theme={"system"}
{
"error": "too many transactions; max is 10000",
"error_detail": {
"code": "TXN_BULK_LIMIT_EXCEEDED",
"message": "too many transactions; max is 10000"
}
}
```
```json 400 theme={"system"}
{
"error_detail": {
"code": "TXN_VALIDATION_ERROR",
"message": "transactions[1]: currency: cannot be blank; destination: either destination or destinations is required, not both.",
"details": {
"index": 1
}
},
"errors": "transactions[1]: currency: cannot be blank; destination: either destination or destinations is required, not both."
}
```
```json 409 theme={"system"}
{
"batch_id": "bulk_305873c0-518a-470c-bf3a-bc3f3e0b562c",
"error": "failed to queue transaction 2 (Reference: sqdup-17372-existing, Source: bln_b4819533-9570-4770-a1a0-25c191da0557, Destination: bln_34111155-4015-4e84-bf7c-13a60794bf0b, Amount: 4.00): transaction validation failed: reference sqdup-17372-existing has already been used. All transactions in this batch have been refunded.",
"error_detail": {
"code": "TXN_DUPLICATE_REFERENCE",
"message": "failed to queue transaction 2 (Reference: sqdup-17372-existing, Source: bln_b4819533-9570-4770-a1a0-25c191da0557, Destination: bln_34111155-4015-4e84-bf7c-13a60794bf0b, Amount: 4.00): transaction validation failed: reference sqdup-17372-existing has already been used. All transactions in this batch have been refunded."
}
}
```
## Need help?
We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool.
To ask questions or discuss issues, please [contact us](mailto:support@blnkfinance.com) or [join our Discord community](https://discord.gg/7WNv94zPpx).
Sign up and manage your ledger with our back-office dashboard. You can invite teammates to collaborate and manage your ledger operations directly from the dashboard.