Skip to main content
POST
Submit withdrawal
The response body shown here is a static example, not live data. After you click Send, your live result appears in a separate panel headed 200 OK. The panel under the status-code tabs is a fixed sample from the spec — its field values (fees, prices, sizes, IDs, timestamps) are placeholders. Use Send, or call the endpoint, for current values.
Submit a withdrawal of collateral to the chain. The request is self-authenticated by a secp256k1 EIP-712 typed-data signature in the body — it does not require the X-API-Key / X-Signature headers. In v0 only withdraw-to-self is supported: the recipient is always the wallet that signed the request (ethereumAddress), so there is no to field.

Response behavior

Asynchronous. A 202 Accepted means the withdrawal passed validation and was queued to the matching engine with status: PENDING. The definitive outcome (applied, or rejected for insufficient free collateral) is delivered asynchronously — poll GET /v1/accountTransferUpdates or subscribe to the account transfer update WebSocket channel and correlate on withdrawalId.

Signing the request

Withdrawals use EIP-712 typed data (eth_signTypedData_v4), so wallets render each field and institutional / MPC signers can whitelist on the domain. Sign this typed data with the wallet that owns ethereumAddress, then split the 65-byte result into {r, s, v} for the signature field. The gateway recovers the signer and rejects mismatches with HTTP 401. Domain
Types
Message
amount is the integer collateral quote-quantum amount (same value as the amount request field). Per-environment domain parameters Complete eth_signTypedData_v4 call (ethers v6 / viem)
The v component must be 0x1b (27) or 0x1c (28); wallets that return 0 / 1 should have 27 added before sending.

Body

application/json
ethereumAddress
string
required

Master EVM address initiating the withdrawal. In v0 this is also the on-chain recipient (withdraw-to-self) — there is no separate destination field.

Pattern: ^(0x|0X)?[0-9a-fA-F]{40}$
Example:

"0x742d35cc6634c0532925a3b844bc9e7595f2bd18"

amount
string
required

Amount to withdraw, as a base-10 integer string in quote quantums (1e9 = $1; for example, 1000000000 represents $1). Requests with an amount below the minimum withdrawal size for the collateral currency are rejected with HTTP 400, for example validation error on field 'amount': must be at least 1000000000 quote quantums. Amounts must be positive, fit in a signed 64-bit integer, and be exactly representable in collateral base units; float-style decimals are rejected.

Pattern: ^[0-9]+$
Example:

"5000000000000"

nonce
string
required

Replay-protection nonce, single-use per (ethereumAddress, accountIndex) — a repeated nonce is rejected with 409. Send the current time as nanoseconds since the Unix epoch (a plain base-10 integer, e.g. 1730000000000000000); the server accepts a timestamp up to 48 hours in the past by default (covers slow multi-approver / MPC custody signing) and up to 24 hours in the future by default (clock skew only) — both bounds are configurable per environment, so treat these as defaults, not guarantees. A legacy opaque nonce (e.g. a UUID) is still accepted for backward compatibility but is deprecated — prefer the nanosecond timestamp form. At most 64 characters.

Required string length: 1 - 64
Example:

"1730000000000000000"

signature
object
required

secp256k1 EIP-712 typed-data signature (r, s, v) over the Withdraw payload (eth_signTypedData_v4). See the POST /v1/withdraw endpoint description for the exact domain, types, and message. Produced by the wallet that owns ethereumAddress; requests whose recovered signer does not match are rejected with HTTP 401.

accountIndex
integer

Trading account to debit. Defaults to 0 when omitted.

Required range: 0 <= x <= 9

Response

Withdrawal accepted and queued to the matching engine. The body carries status: PENDING and a withdrawalId; the terminal outcome is delivered on the account transfer update stream.

withdrawalId
string
required

Server-generated identifier (UUID) correlating this withdrawal with the matching AccountTransferUpdate on the account transfer update stream.

Example:

"b3f1c2d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d"

ethereumAddress
string
required

20-byte EVM address as hex: optional 0x or 0X prefix and exactly 40 hexadecimal digits. API responses normalize to lowercase af after 0x.

Pattern: ^(0x|0X)?[0-9a-fA-F]{40}$
accountIndex
integer
required

Account index (account index, 0–9). Identifies the account for orders, positions, fills, and API keys.

Required range: 0 <= x <= 9
amount
string
required

Withdrawal amount echoed back as a human-readable decimal in quote currency (quote resolution 1e9), matching how the amount is reported on the account transfer update feed.

Examples:

"5000"

"1.5"

status
enum<string>
required

Synchronous status of a submitted withdrawal. Always PENDING on the 202 response — the withdrawal has been queued to the matching engine but not yet applied. The terminal outcome (APPLIED, REJECTED_INSUFFICIENT_COLLATERAL, ...) is delivered asynchronously on the account transfer update stream (see AccountTransferUpdate).

Available options:
PENDING
submittedAt
integer<int64>
required

Server receive timestamp (epoch microseconds).