List withdrawals

GET /api/v1/withdrawals read:inventory

Lists your withdrawals, newest first by requested_at. RIP.FUN-initiated withdrawals appear here too: withdrawals we open on your behalf (e.g. during contract termination or inventory retrieval) are returned alongside your own — they follow ACKNOWLEDGED → LABEL_PURCHASED → COMPLETED and skip REQUESTED, so expect rows you did not create. Paged like every other list: read pagination.has_more and pass pagination.next_offset back as ?offset.

Try it GET /api/v1/withdrawals?limit=10

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

response

Not run yet. Press Run to make a live call against https://service.rip.fun (through this demo's server-side proxy; the API key never reaches the browser).

curl (tracks the inputs above)
curl -X GET 'https://service.rip.fun/api/v1/withdrawals?limit=10' \
  -H 'X-API-Key: rip_…'

Request fields

FieldTypeRequiredDescription
statusquery stringREQUESTED | ACKNOWLEDGED | IN_TRANSIT | LABEL_PURCHASED | COMPLETED | CANCELLED — matched exactly; an unrecognized value returns 400
limit / offsetquery intlimit 1..100 default 50; offset 0..10_000 default 0. Non-integer values are a 400 (invalid_pagination). The response carries a pagination object { limit, offset, has_more, next_offset } beside the array

Response fields (data)

FieldDescription
withdrawals[]Same row shape as POST /withdrawals (without items)

Errors

StatusCodeWhen
400invalid statusstatus is not one of the accepted values

See Errors for the response envelope and the full code list.