Skip to main content

Bridge transfer status

GET 

/v1/data/bridge/status

Tracks a bridge transfer started via /v1/actions/swap/x-chain by polling the bridge's own tracking API. status is one of PENDING, DONE, FAILED, TRANSFER_REFUNDED, INVALID, NOT_FOUND, PARTIAL_SUCCESS. NOT_FOUND is normal in the first seconds after submission (indexer lag) — keep polling. toHash is the destination-chain transaction when the tracker exposes it. Responses are not cached.

Plain-text reference — GET /v1/data/bridge/status

Parameters

ParameterInTypeRequiredDescription
bridgequerystringyesThe bridge value from the executed quote
fromChainIdquerystringyesSource chain ID of the transfer
toChainIdquerystringyesDestination chain ID
txHashquerystringnoSource-chain transaction hash of the executed bridge transaction (required unless orderId)
tokenInquerystringnoBridged input token address — REQUIRED for Stargate (pool-keyed tracker), ignored by most bridges
tokenOutquerystringnoBridged output token address — REQUIRED for Stargate
orderIdquerystringnoIntent order id for order-based bridges (Mayan)

Response 200

FieldTypeDescription
successboolean
dataobjectInformational payload. null when the endpoint only builds calldata.
data.bridgestring
data.statusPENDING, DONE, FAILED, TRANSFER_REFUNDED, INVALID, NOT_FOUND, … (7 values)
data.messagestring
data.fromHashstring
data.toHashstringDestination-chain tx hash when known
data.detailsobjectThe tracker's raw response payload

Example response

{
"success": true,
"data": {
"bridge": "string",
"status": "PENDING",
"message": "string",
"fromHash": "string",
"toHash": "string"
}
}

Request

Responses

Transfer status