Skip to main content
This endpoint turns off an Expo push token for your account. Pacifica stops sending mobile_push notifications to it. Call it when the user signs out of the app.

Operation Type (for Signing)

Request Body

FieldTypeNeedDescriptionExample
”account”stringrequiredUser’s wallet address42trU9A5…
“signature”stringrequiredCryptographic signature5j1Vy9Uq…
“timestamp”integerrequiredCurrent timestamp in milliseconds1716200000000
”expo_push_token”stringoptionalExpo push token to turn off. Up to 512 charactersExponentPushToken[xxxx]
“device_id”stringoptionalInstallation key. Turns off the tokens of this installation. Up to 256 charactersb7f3c1a9…
“expiry_window”integeroptionalSignature expiry in milliseconds30000
”agent_wallet”stringoptionalAgent wallet address69trU9A5…
Send 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_id invalid_expo_push_token. A request without expo_push_token or device_id returns 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

Code Example (Python)