Skip to main content
POST
Configure session as a withdraw and return calldata

Authorizations

X-API-Key
string
header
required

Server API key (sk_live_...)

Path Parameters

accountTypeId
string
required

Account Type slug

Minimum string length: 1
accountId
string<uuid>
required

RFC 4122 UUID

Example:

"8e9f4d67-51ad-49aa-a502-2f569aaf7399"

intentId
string<uuid>
required

RFC 4122 UUID

Example:

"8e9f4d67-51ad-49aa-a502-2f569aaf7399"

Body

application/json
destinationChainId
required

EVM chain ID

Required range: x >= 1
Example:

8453

amount
string
required

Ignored when isMaxWithdraw is true.

Pattern: ^(?:0|[1-9][0-9]*)$
isMaxWithdraw
boolean
default:false

Redeems every source-chain position. Cross-chain Relay calldata is embedded in the atomic withdrawal transaction.

Response

Success

status
string
required
Allowed value: "success"
data
object
required
Last modified on July 24, 2026