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 |
”expiry_window” | integer | optional | Signature expiry in milliseconds | 30000 |
”agent_wallet” | string | optional | Agent wallet address | 69trU9A5… |
Signing
This request has no fields of its own. Sign an emptydata object:
Response
- Status 200: Successfully retrieved notification preferences
| Field | Type | Description |
|---|---|---|
”master_enabled_channels” | array | Channels that are on in the master preference:“in_app""mobile_push""web_push" |
"preferences” | array | One entry for each notification type that you can configure |
”notification_type” | string | Notification type |
”enabled_channels” | array | Channels that are on for this type |
preferences always lists all eight types, in the order above. A type that you never set has an empty enabled_channels list. A new account has empty lists everywhere.
- Status 400: Invalid request parameters or signature
- Status 403: The account doesn’t exist. An account exists after its first deposit
- Status 429: Rate limit exceeded
- Status 500: Internal server error