Deposit history

GET /api/v1/wallet/deposits wallet:read

The deposits CardOS has seen for one end-user: source chain and token, amount, transaction hash and confirmation state. deposit.credited fires as a webhook when one lands, so poll this only for reconciliation.

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

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

response
403 10ms 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/deposits?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
deposits[].chain_in / token_in / amount / tx_hashWhat arrived, from where
deposits[].status / expected_output / confirmed_atConfirmation state and the USDC credited
linked_internal_userfalse when the end-user has no linked deposit identity yet — deposits[] is [] then