The crypto transaction object
string
Unique identifier with
trxn_ prefix (e.g., trxn_abc123def456).string
Always
"crypto_transaction".string
Transaction amount (string to preserve precision).
string
Blockchain transaction hash.
string
Source of the transaction:
manual_entry or blockchain.string
When the transaction occurred (ISO 8601).
string
Currency code (e.g.,
BTC, ETH).string
Sending address ID. May be
null.string
Sending address. May be
null.string
Receiving address ID.
string
Receiving address.
array
Transaction allocations to invoices.
string
When the record was created (ISO 8601).
string
When the record was last updated (ISO 8601).
List crypto transactions
integer
default:"1"
Page number for pagination. Results are returned 25 items per page.
Response
Get crypto transaction
string
required
The transaction’s ID (e.g.,
trxn_abc123def456).Response
Create crypto transaction
string
required
The receiving address ID (e.g.,
addr_abc123). Must belong to your account.string
required
The transaction amount (as a string to preserve precision).
string
required
The currency code (e.g.,
BTC, ETH).string
required
The blockchain transaction hash/ID.
string
The transaction timestamp (ISO 8601 format). Defaults to current time.
string
The sending address ID (e.g.,
addr_xyz789).Response
Error responses
Address not found
Unsupported currency
The allocation object
Sandbox support
The API respects sandbox scoping. If your API token is associated with a sandbox, you can only access transactions created in that sandbox. Manually created transactions will be isolated from production data.