Get a send

GET /api/v1/sends/:send_id sends:create · packs:read

The poll companion to POST /sends, and the record afterwards. Same row shape as the 202, with items[] filled in as the on-chain transactions land. Partner-scoped: a send that is not yours is a 404, not a 403.

Try it GET /api/v1/sends/0

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"
}
curl (tracks the inputs above)
curl -X GET 'https://service.rip.fun/api/v1/sends/0' \
  -H 'X-API-Key: rip_…'

Response fields (data)

FieldDescription
statusin_progress while items are still going out; complete when they all landed; complete_with_errors when any failed
items[].status / tx_hash / errorPENDING → SENDING → SENT | FAILED, the transaction that delivered it, and the failure reason if it did not
items[].buyback_registered_at / buyback_errorWhether the winner can sell that item back

Errors

StatusCodeWhen
404not_foundnot one of your sends
400invalid_send_idsend_id is not a positive integer

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