Skip to main content
Use these endpoints to check the current state of a sponsorship request. You can look up a request either by its UUID (assigned at creation) or by the on-chain transaction hash if the request has been relayed.

Get by UUID

GET /sponsorship/:id
string
required
UUID of the sponsorship request, returned when you called POST /sponsorship/request.
string
required
UUID of the sponsorship request.
string
required
Ethereum address submitted for sponsorship.
string
required
Current lifecycle status of the sponsorship request. See the status table below.
string
required
ISO 8601 timestamp of when the request was created.
string
IP address of the client that submitted the request.
string
User-agent string from the original request, or null if not captured.

Get by transaction hash

GET /sponsorship/tx/:hash Use this endpoint to find a sponsorship request using an on-chain transaction hash. This is useful if you have a transactionHash from a relay record and want to trace it back to the originating sponsorship request.
string
required
The on-chain transaction hash. Accepts any non-empty string up to 1,024 characters.

Sponsorship status values

Status transitions are strictly enforced: pendingapproved or rejected, approvedrelayed, relayedcompleted or failed. Terminal states (rejected, completed, failed) cannot transition further.

Errors

200