Operation Type (for Signing)
Request Body
| Field | Type | Need | Description | Example |
|---|---|---|---|---|
”account” | string | required | User’s wallet address | 42trU9A5… |
“signature” | string | required | Cryptographic signature | 5j1Vy9Uq… |
“timestamp” | integer | required | Current timestamp in milliseconds | 1716200000000 |
”agent_wallet” | string | optional | Agent wallet address | 69trU9A5… |
“expiry_window” | integer | optional | Signature expiry in milliseconds | 30000 |
Signing
Thedata object is empty. For the request above, the message to sign is:
Response
- Status 200: Success
While 2FA is on, factor changes also need a proof.
protected_actions lists only withdrawals.
Each entry in factors has these fields:
An account that never turned on 2FA returns empty lists and
"recovery_keys_remaining": 0.
- Status 400: Invalid request parameters or signature
- Status 403: The account is a subaccount, or it does not exist
- Status 500: Internal server error
- Status 503: The two-factor service is unavailable. Retry later