# Enable mobile push notifications

`POST https://api.cryptohopper.com/v1/user/enableallmobilepushnotifications`

Part of [Users](https://www.cryptohopper.com/api-documentation/api-reference/users.md) in the Cryptohopper API reference.

Registers a mobile device for push notifications. Without permissions all notification types are enabled; with permissions only the listed types are enabled and the others are turned off.

OAuth scope: `user`

Without player_id the endpoint still returns HTTP 200, with the message "You need to provide a valid player ID".

## Headers

| Name | Type | Required | Description |
|---|---|---|---|
| `permissions` | string | no | Optional comma-separated list of notification types to enable: config_error, on_first_start, on_trigger, on_panic_start, on_panic_end, order_placed, trade_completed, order_cancelled. |
| `access-token` | string | yes | The OAuth access token of the user. |
| `player_id` | string | no | Push notification player ID of the device. Required. |

## Example request

```bash
curl -X POST "https://api.cryptohopper.com/v1/user/enableallmobilepushnotifications" \
  -H "access-token: YOUR_ACCESS_TOKEN"
```

## Response

Example response (illustrative values):

```json
{
    "data": "Mobile notifications updated"
}
```

Status codes: 200. Errors return JSON with `status`, `error` and `message`, plus a numeric `code` when the error comes from the API itself rather than the gateway.