Skip to main content
Transactions show the activity in your Ledig business account. Use them to match deposits and payments with records in your own system. For a payment currently in progress, use the transfer endpoint.

List transactions

For example, request the last 30 days of USDT transactions:
This fictional response excerpt shows a completed USDT payout:
Amounts are decimal strings. In this example, isCredit: false means an outgoing amount and isFiat: false identifies a crypto transaction. Use the returned cursor for the next page. Stop when pagination.nextCursor is absent, as in this final-page example. See Pagination.

Read one transaction

Call GET /v1/transactions/{id} using an ID returned in your history. The response may include: Use receipt references or download links when they are returned. Some fields are only present for relevant transaction types.

Deposits awaiting release

A deposit can appear in history before it is available to spend. A deposit receipt can have data.recordKind: "deposit_receipt" and data.affectsBalance: false. If displayStatus is frozen, the funds are held and are not yet available. When the deposit is credited, the transaction replaces the receipt-only entry. Looking up the original receipt ID can return that transaction. Match records using the returned ID and reference so you do not count the same deposit twice.

Check available funds

Use Balances for your available and reserved amounts. Do not calculate a spendable balance by adding every history entry: some records are informational and have data.affectsBalance: false.