> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sequenzy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Unsubscribe a Push Device

> Stop sending push to a device

# Unsubscribe a Push Device

Marks a device `unsubscribed` so it stops receiving push, for example when a person signs out of your app. Requires the `subscribers:write` scope.

This does not revoke the browser or app permission. A browser that still allows notifications registers again, unlinked from the contact, the next time the web SDK syncs; your app registers again whenever it calls [Register a push device](./register-device). To stop a browser for good, call `sequenzy.unsubscribeFromPush()` on your site or have the visitor turn off notifications.

## Request

<ParamField path="deviceId" type="string" required>
  The device ID from [List push devices](./list-devices) or [Register a push
  device](./register-device).
</ParamField>

```bash theme={null}
curl -X DELETE "https://api.sequenzy.com/api/v1/push/devices/dev_123" \
  --header "Authorization: Bearer $SEQUENZY_API_KEY"
```

## Responses

<ResponseExample>
  ```json 200 theme={null}
  {
    "success": true,
    "deviceId": "dev_123",
    "message": "Device unsubscribed. It stops receiving push until your site or app registers it again."
  }
  ```

  ```json 401 theme={null}
  {
    "error": "Invalid API key"
  }
  ```

  ```json 403 theme={null}
  {
    "error": "API key is missing required scope: subscribers:write"
  }
  ```

  ```json 404 theme={null}
  {
    "error": "Device not found"
  }
  ```
</ResponseExample>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.