mobile_push notifications to it. Call it when the user signs out of the app.
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 |
”expo_push_token” | string | optional | Expo push token to turn off. Up to 512 characters | ExponentPushToken[xxxx] |
“device_id” | string | optional | Installation key. Turns off the tokens of this installation. Up to 256 characters | b7f3c1a9… |
“expiry_window” | integer | optional | Signature expiry in milliseconds | 30000 |
”agent_wallet” | string | optional | Agent wallet address | 69trU9A5… |
expo_push_token or device_id. If you send both, Pacifica uses expo_push_token only. Leave out the field that you don’t send, in the request and in the signed data.
Pacifica turns off only tokens of the signing account. An unknown token or device_id doesn’t cause an error.
You can sign this request with the account key or with an agent wallet.
To get notifications on the device again, call Register Expo device.
Response
- Status 200: Token turned off
- Status 400: Invalid request parameters or signature. A token with a bad format returns
error_idinvalid_expo_push_token. A request withoutexpo_push_tokenordevice_idreturns this error:
- Status 403: The account doesn’t exist. An account exists after its first deposit
- Status 429: Rate limit exceeded
- Status 500: Internal server error