Use the Blnk CLI to list, create, and update transactions on your Core instance.
Use the transactions command to list transfers, inspect a single post, create transactions interactively, and commit, void, or refund inflight work. Reach for this command when you are debugging money movement or testing a flow on Core.
Command
Alias
Description
list
l
Browse transfers with filters; add --id for one transaction
Monitor money movement in a paginated table with amount, currency, status, and related IDs.Filter by --status, --currency, or --balance-id to audit queued work, applied posts, or activity on one account.
blnk transactions list [options]
Options
Option
Type
Default
Description
--{field}
string
—
Filter by any indexed field (for example --status APPLIED, --currency "USD,EUR").
-p, --page
integer
1
Page number.
--per-page
integer
10
Results per page.
-h, --help
boolean
—
Show help for this command.
Usage
1
List all transactions
Run the command to view a paginated table of transactions:
blnk transactions list
Filter and paginate:
blnk transactions list --page 3 --per-page 25blnk transactions list --status APPLIED --currency "USD,EUR"blnk transactions list --balance-id bln_abc123 --status APPLIED
Inspect one transaction end to end: source, destination, reference, status, and metadata.Pass --json when you need precision, inflight flags, or parent/child links exactly as Core returns them.
blnk transactions list --id <transaction-id> [options]
Options
Option
Type
Required
Description
--id
string
Yes
Transaction ID to fetch (for example txn_fa19841f-faa5-4838-9295-b7278a4ff71d).
--json
boolean
No
Print the full API object as JSON instead of a formatted summary.
-h, --help
boolean
No
Show help for this command.
Usage
1
Get one transaction
Run the command with a transaction ID:
blnk transactions list --id txn_fa19841f-faa5-4838-9295-b7278a4ff71d
Post a transfer between balances (or indicators) through prompts for amount, precision, parties, reference, and inflight options.Handy for quick manual tests; multi-leg or high-volume flows should go through your application integration instead.
blnk transactions create [options]
The interactive flow covers common fields. For complex multi-leg or bulk transactions, use your application integration against Core directly.
ArgumentsThe CLI prompts for these values. They are not passed on the command line.
Argument
Type
Required
Description
amount
string
Yes
Transaction amount. Prompt: amount >
precision
integer
Yes
Amount precision (for example 100 for cents). Prompt: precision >
currency
string
Yes
Currency code. Prompt: currency >
source
string
Yes
Source balance ID or indicator. Prompt: source >
destination
string
Yes
Destination balance ID or indicator. Prompt: destination >
reference
string
Yes
Unique reference for the transaction. Prompt: reference >
description
string
Yes
Short description. Prompt: description >
allow_overdraft
boolean
No
Whether overdraft is allowed. Prompt: allow overdraft >
inflight
boolean
No
Whether the transaction is inflight. Prompt: inflight >
meta_data
object
No
Optional metadata as JSON. Prompt: metadata (json) >. Press Enter to skip.
Options
Option
Type
Description
--json
boolean
After a successful create, print the full API response as JSON.
Move an existing transaction through its lifecycle: commit inflight funds, void before settlement, or refund after apply.Supply the transaction ID and exactly one of --commit, --void, or --refund.