value-transfer

Poll a transfer to completion

Upstream events collapsed into the three stages the Progress screen renders, plus terminal and pollAfterMs so the client neither interprets event names nor owns the cadence. Re-poll after pollAfterMs until terminal is true. txHash speeds up the lookup. Only call this for a quote with trackable: true — a same-chain send has no upstream record.

get/value-transfer/status/{quoteId}

Path parameters

quoteIdstring required

Query parameters

txHashstring required

Response

Current transfer status

status'PENDING' | 'PROCESSING' | 'SUCCEEDED' | 'FAILED' | 'UNKNOWN' required
stage'sent' | 'bridging' | 'delivered' required

Furthest stage reached. Derived from upstream events server-side so a new event name never needs a client release.

terminalboolean required

True once the transfer has settled either way. Stop polling when set.

pollAfterMsobject nullable required

How long to wait before polling again, in ms. Null once terminal. Server-owned so the cadence can be tuned without a client release.

explorerUrlstring

LayerZero Scan link for the transfer — the per-leg tx detail, so the client does not need a timeline of its own.

Example response

{
  "status": "PROCESSING",
  "stage": "bridging",
  "explorerUrl": "https://layerzeroscan.com/tx/0xabc…"
}

Changes

No recorded changes to this endpoint across all 1 revision of this API.