Check status by request ID
Send aGET request to /sponsorship/:id using the UUID you received when you created the request.
Sponsorship status lifecycle
completed, rejected, and failed are terminal states. Once a request reaches one of these statuses it will not change.
The relay worker retries failed relay attempts up to 5 times before marking the request as
failed. Each attempt is recorded as a separate entry in relayTransactions, with relayAttempt incrementing from 1.Check relay transaction details
Each sponsorship request can have one or more relay transaction records. Retrieve a specific relay transaction by its UUID to see low-level details including the on-chain transaction hash, submission time, confirmation time, and any failure reason.status field follows its own lifecycle: queued → submitted → confirmed (or failed).
Look up by transaction hash
If you already have the on-chain transaction hash, you can find the associated sponsorship request directly.Polling guidance
Poll/sponsorship/:id every few seconds until the status reaches a terminal state (completed, rejected, or failed). Most requests complete within 30 seconds under normal network conditions. If the status remains pending or approved for more than a few minutes, check the dashboard for service health.