Use this endpoint to inspect the relay transaction associated with an approved sponsorship request. A relay transaction is created when a sponsorship moves fromDocumentation 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.
approved to relayed status. You can use it to track whether the on-chain transaction has been broadcast and confirmed.
Request
GET /relay/:id
UUID of the relay transaction record. This is distinct from the sponsorship request ID — obtain it from the relay record linked to your sponsorship.
Response
UUID of this relay transaction record.
UUID of the sponsorship request that triggered this relay. Use this to correlate the relay with the originating request.
Current status of the relay transaction. See the status table below.
Number of times relay submission has been attempted for this record. Starts at
1 on first submission.On-chain transaction hash once the transaction has been broadcast, or
null if it has not been submitted yet.ISO 8601 timestamp of when the transaction was first broadcast to the network, or
null if not yet submitted.ISO 8601 timestamp of when the transaction was mined and confirmed, or
null if not yet confirmed.ISO 8601 timestamp of when the relay entered a failed state, or
null if it has not failed.Human-readable description of why the relay failed, or
null if there is no failure.Relay status values
| Status | Meaning |
|---|---|
queued | The relay is waiting to be submitted on-chain. The transaction has not been broadcast yet. |
submitted | The transaction has been broadcast to the network and is awaiting mining. |
confirmed | The transaction has been mined and confirmed on-chain. |
failed | The relay encountered an error. Check failureReason and failedAt for details. |
Errors
| Status | Cause |
|---|---|
400 | The :id is not a valid UUID format. |
404 | No relay transaction found with the given ID. |