approved to relayed status. You can use it to track whether the on-chain transaction has been broadcast and confirmed.
Request
GET /relay/:id
string
required
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
string
required
UUID of this relay transaction record.
string
required
UUID of the sponsorship request that triggered this relay. Use this to correlate the relay with the originating request.
string
required
Current status of the relay transaction. See the status table below.
integer
required
Number of times relay submission has been attempted for this record. Starts at
1 on first submission.string
On-chain transaction hash once the transaction has been broadcast, or
null if it has not been submitted yet.string
ISO 8601 timestamp of when the transaction was first broadcast to the network, or
null if not yet submitted.string
ISO 8601 timestamp of when the transaction was mined and confirmed, or
null if not yet confirmed.string
ISO 8601 timestamp of when the relay entered a failed state, or
null if it has not failed.string
Human-readable description of why the relay failed, or
null if there is no failure.