For the complete documentation index, see llms.txt. This page is also available as Markdown.

Execute a bridge step

Execute a bridge step

post

Submit a signed step of a Hyperliquid withdrawal.

Withdrawals only. A deposit's transactions are signed and broadcast by you on the origin chain and never pass through this endpoint — if a quote's execution_type is evm_transaction, you do not need this call.

target_url must be a URL the quote's steps gave you. It is checked against a strict host allowlist and only the withdrawal action is accepted, so this cannot be used as a general-purpose proxy. body is that step's payload with your signature filled in.

⚠️ This moves funds. A 2xx means the withdrawal was accepted; a refusal is returned as a 422 carrying the reason rather than a success envelope, so a 2xx can be trusted. Poll /api/v1/perp/bridge/status with the quote's request_id to see it complete on the destination chain.

Authorizations
apikeystringRequired

API key for authentication

Body

A signed withdrawal step to submit.

target_urlstringRequired

Submission URL taken from the quote's steps. Checked against a strict host allowlist, so an arbitrary URL is rejected.

Example: https://<allowlisted-host>/authorize?signature=0xabc
Responses
200

Upstream response for the submitted withdrawal step

application/json
post/api/v1/perp/bridge/execute

Last updated

Was this helpful?