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 rename | c9f0f895-fb98-4b91-a3b5-6e9e7c2f1d4a |
”label” | string | required | New name for the factor. 1 to 64 characters, with no control characters and no leading or trailing spaces | Phone |
”expiry_window” | integer | optional | Signature expiry in milliseconds | 30000 |
Signing
Signfactor_id and label as the data object. For the request above, the message to sign is:
Response
- Status 200: Factor renamed
- Status 400: Invalid request parameters, label, or signature
- Status 403: The account is a subaccount, or it does not exist
- Status 422: No factor on the account has this
factor_id(unknown factor) - Status 500: Internal server error
- Status 503: The two-factor service is unavailable. Retry later