Transfer status
Use this one unless you are migrating existing aggregator code — see GET /status for that.
Key by txHash for contract-call routes, or by depositAddress (+ depositMemo) for deposit-based routes.
Anonymous — no API key, so it is safe to call straight from your frontend. Resolves our own settlement lifecycle first and falls back to the upstream router’s status for swaps we did not settle ourselves.
Poll until the status is terminal (DONE or FAILED). A cross-chain route has no receiving leg until the destination transaction lands — that is normal progress, not a stall.
Query Parameters
Response
Transfer identifier (the Warp messageId). Stable across both legs.
Bridging tool — always hypermid.
"hypermid"
Top-level status. Poll until DONE or FAILED.
NOT_FOUND, INVALID, PENDING, DONE, FAILED Finer-grained status, using the standard aggregator substatus vocabulary.
Human-readable explanation.
Sender (source) address.
Recipient (destination) address.
Source-chain leg. Absent until the source tx is indexed.
Destination-chain leg. Absent until the dest tx is mined (DONE/REFUNDED).
Integrator metadata.