Skip to main content
GET
curl
Didit’s transaction list API returns monitored transactions with their Travel Rule state. Each nested travel_rule includes the same nullable proof request relation as transaction detail: request_id, request status, expires_at and nullable proof. Request status is separate from the proof verdict and saved transfer decision.

Authorizations

x-api-key
string
header
required

Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is wrong, revoked or expired; 403 means no key was sent, the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.

Query Parameters

limit
integer
default:50

Page size. Defaults to 50 when omitted. There is no enforced maximum, but keep pages small for latency.

Required range: 1 <= x <= 1000000
offset
integer
default:0

Zero-based offset of the first record to return. Prefer following the next URL from the previous page.

Required range: 0 <= x <= 1000000
travel_rule_status
string

Return only transactions whose Travel Rule transfer is in this exact status (for example ON_HOLD or AWAITING_COUNTERPARTY). count follows this filter; total_transactions still counts every transaction in the application.

assignee
string

Comma-separated; a transaction matches when it meets any value. unassigned is what nobody holds yet, rules is what the rules decided on their own without a reviewer, and a member email matches the reviewer assigned to it. me is the signed-in Console reviewer, so an API key sending me gets 400.

Response

Paginated list of transaction summaries, newest first.

count
integer

Capped count of matching transactions (exact up to 100, capped thereafter). Use total_transactions for the true count when paginating.

next
string | null

Absolute URL of the next page, or null on the last page.

previous
string | null

Absolute URL of the previous page, or null on the first page.

total_transactions
integer

Exact total count of (non-deleted) transactions for the application. Present on paginated responses.

results
object[]
Last modified on November 14, 2026