Wallet ledger

GET /api/v1/wallet/ledger wallet:read

The full audit trail of one end-user's wallet: deposits credited, purchase reserves, settlements and refunds, each with the running balance after it. source / source_id tie an entry back to what caused it (e.g. purchase:123).

Try it GET /api/v1/wallet/ledger?external_user_id=demo-explorer&limit=10

These inputs are shared across all docs pages, so an id entered here carries over.

response
403 13ms preloaded server-side with the default context
object · 3 keys
{
  "success": false,
  "message": "Mystery partner API key required",
  "error": "This endpoint requires an API key linked to a mystery partner account"
}
tracks the inputs above
curl -X GET 'https://service.rip.fun/api/v1/wallet/ledger?external_user_id=demo-explorer&limit=10' \
  -H 'X-API-Key: rip_…'

Request fields

FieldTypeRequiredDescription
external_user_id / wallet_addressquery stringyesWhich end-user
limit / offsetquery intPagination

Response fields (data)

FieldDescription
entries[].entry_type / amount / amount_usdcWhat happened and for how much
entries[].balance_after / reserved_afterRunning balances after this entry
entries[].source / source_id / description / created_atCause linkage and timestamp