Retrieve transaction history for a participant.
created_at. The from and to parameters filter on created_at (when the journal entry was recorded). Use event_from / event_to to filter by the originating event’s event_timestamp instead — entries without an event fall back to their created_at. Both pairs can be used simultaneously (AND semantics).
Each event-driven transaction includes an event_timestamp field in the response, showing when the originating event occurred.
API key passed in the X-API-Key header.
Participant ID
Maximum number of results (default 50, max 200)
x >= 1Pagination cursor from previous response
Filter by asset ID
Filter by balance bucket
AVAILABLE, HELD, DEFERRED Start of time window (RFC 3339) — filters on system ingestion time
End of time window (RFC 3339) — filters on system ingestion time
Start of event occurrence window (RFC 3339) — filters on event_timestamp
End of event occurrence window (RFC 3339) — filters on event_timestamp