Transfer status (compatible)
A drop-in replacement for the common aggregator status endpoint. Reach for it only if you already have a client written against that shape; for new integrations use GET /v1/status, which needs no API key.
Requires a partner key. Key it by txHash (source, destination or refund transaction hash, or the bridge message id) for contract-call routes, OR by depositAddress (+ depositMemo on memo-chains) for deposit-based routes.
The response follows the standard aggregator shape — status ∈ with a finer substatus, plus sending and receiving legs — so an existing client works unchanged. Poll until terminal.
Authorizations
Soft-auth read routes accept x-api-key with a publishable or partner key; money-moving routes require a secret partner key in Authorization: Bearer.
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.