Skip to main content
GET
/
v1
/
participants
/
{id}
/
activity
/
history
Get participant transaction history
curl --request GET \
  --url https://api.scrip.dev/v1/participants/{id}/activity/history \
  --header 'X-API-Key: <api-key>'
{
  "data": [
    {
      "amount": "100.00",
      "asset_id": "550e8400-e29b-41d4-a716-446655440001",
      "bucket": "AVAILABLE",
      "created_at": "2024-01-15T10:30:00Z",
      "created_by_api_key_id": "770e8400-e29b-41d4-a716-446655440000",
      "description": "Credit: 10x bonus",
      "event_id": "660e8400-e29b-41d4-a716-446655440000",
      "event_timestamp": "2025-01-15T10:30:00Z",
      "journal_entry_id": "550e8400-e29b-41d4-a716-446655440000"
    }
  ],
  "pagination": {
    "has_more": true,
    "next_cursor": "YWJjMTIz"
  }
}
Returns a chronological list of balance-affecting operations for a participant. This includes credits, debits, holds, releases, and forfeits, each with full journal entry details such as amount, asset, timestamp, and source. Use this endpoint to build participant-facing transaction histories or to audit how a participant’s balance changed over time. Results are paginated and ordered by 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.
For usage patterns and examples, see the Participants guide.

Authorizations

X-API-Key
string
header
required

API key passed in the X-API-Key header.

Path Parameters

id
string<uuid>
required

Participant ID

Query Parameters

limit
integer
default:50

Maximum number of results (default 50, max 200)

Required range: x >= 1
cursor
string

Pagination cursor from previous response

asset_id
string<uuid>

Filter by asset ID

bucket
enum<string>

Filter by balance bucket

Available options:
AVAILABLE,
HELD,
DEFERRED
from
string<date-time>

Start of time window (RFC 3339) — filters on system ingestion time

to
string<date-time>

End of time window (RFC 3339) — filters on system ingestion time

event_from
string<date-time>

Start of event occurrence window (RFC 3339) — filters on event_timestamp

event_to
string<date-time>

End of event occurrence window (RFC 3339) — filters on event_timestamp

Response

Transaction history

data
object[]

Data contains the list of items

pagination
object

Pagination contains cursor information for fetching more results