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.Documentation Index
Fetch the complete documentation index at: https://docs.arcpass.vibepas.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Get by UUID
GET /sponsorship/:id
UUID of the sponsorship request, returned when you called
POST /sponsorship/request.UUID of the sponsorship request.
Ethereum address submitted for sponsorship.
Current lifecycle status of the sponsorship request. See the status table below.
ISO 8601 timestamp of when the request was created.
IP address of the client that submitted the request.
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.
The on-chain transaction hash. Accepts any non-empty string up to 1,024 characters.
Sponsorship status values
| Status | Meaning |
|---|---|
pending | The request has been received and is awaiting review. |
approved | The request passed eligibility checks and is queued for relay. |
relayed | A relay transaction has been submitted on-chain. |
completed | The relay transaction was confirmed on-chain. |
rejected | The request failed eligibility checks and will not be sponsored. |
failed | The relay transaction failed after being submitted. |
pending → approved or rejected, approved → relayed, relayed → completed or failed. Terminal states (rejected, completed, failed) cannot transition further.
Errors
| Status | Cause |
|---|---|
400 | The :id is not a valid UUID format. |
404 | No sponsorship request found with the given ID or transaction hash. |
200