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 |
”factor_id” | string | required | ID (UUID) of the factor to remove | c9f0f895-fb98-4b91-a3b5-6e9e7c2f1d4a |
”proof” | object | required | Proof. A recovery key works. Not part of the signed payload. See Proofs | |
”expiry_window” | integer | optional | Signature expiry in milliseconds | 30000 |
Signing
Signfactor_id as the data object. Do not sign proof. For the request above, the message to sign is:
Response
- Status 200: Factor removed
- Status 400: Invalid request parameters or signature
- Status 401: The proof is wrong, expired, or already used
- Status 403: The account is a subaccount, or it does not exist
- Status 422: The factor cannot be removed. The
errorfield says why:
- Status 429: Too many proof attempts
- Status 500: Internal server error
- Status 503: The two-factor service is unavailable. Retry later