# Configure notification alert settings.

`PUT /notification_settings`

> Wheelhouse Revenue Management API. Web version: https://docs.usewheelhouse.com/rm/reference/rm-update-notification-settings · OpenAPI spec: https://docs.usewheelhouse.com/rm/openapi.yaml · Operation ID: `rmUpdateNotificationSettings` · Tag: Notifications

Enables or disables which alerts the authenticated user receives. Only the settings included in the request are affected — a setting is created when `enabled` is `true` and removed when `enabled` is `false`. Any `event`/`channel` pair not included is left unchanged. Enabling an already-enabled setting (or disabling one that is already off) is a no-op. Returns the user's documented alert settings after the update. A setting stored under an event name outside that list is left unchanged and omitted.

## Request

`PUT https://api.usewheelhouse.com/ss_api/v1/notification_settings`

Authentication: send your RM API key in the `X-Integration-Api-Key` header (see https://docs.usewheelhouse.com/rm/authentication.md). Modifies data; read-only keys get `403 Forbidden`.

### Request body (`application/json`, required)

- `settings` (array of object, required): Alert settings to update.
  - `event` (string, required, one of: `price_posting_error`, `market_report_updated`, `reminder`, `sub_user_invite`, `new_listing_created`, `report_shared`, `report_comment_reply`, `report_comment_mention`, `comp_set_v2_shared`, `api_spend_alert`): The alert event type.
  - `channel` (string, required, one of: `inapp`, `email`): The delivery channel the alert is sent on.
  - `enabled` (boolean, required): Whether the user should receive this alert on this channel.

### Example request

```bash
curl -X PUT 'https://api.usewheelhouse.com/ss_api/v1/notification_settings' \
  -H 'X-Integration-Api-Key: <your RM API key>' \
  -H 'Content-Type: application/json' \
  -d '{
  "settings": [
    {
      "event": "price_posting_error",
      "channel": "inapp",
      "enabled": true
    }
  ]
}'
```

Only required parameters and body fields are filled in, with placeholder values. Add the optional ones you need from the lists above; some are required in combination, as their descriptions say.

## Responses

### 200

Array of the user's active notification settings after the update.

Body (`application/json`): array of object `notification_setting`

A single alert delivery setting. The presence of an `event`/`channel` pair means the user receives that alert on that channel; its absence means they do not.

- `event` (string, required, one of: `price_posting_error`, `market_report_updated`, `reminder`, `sub_user_invite`, `new_listing_created`, `report_shared`, `report_comment_reply`, `report_comment_mention`, `comp_set_v2_shared`, `api_spend_alert`): The alert event type.
- `channel` (string, required, one of: `inapp`, `email`): The delivery channel the alert is sent on.

Example shape (generated from the schema; placeholder values, not a real response):

```json
[
  {
    "event": "price_posting_error",
    "channel": "inapp"
  }
]
```

### 400

An unknown event or channel was provided.

### 401

API key authorization failed.

### 403

The API key is read-only and may not be used to update notification settings.

### 429

Rate limit exceeded — the API key has sent too many requests. Wait before retrying. See the **Rate Limits** section in the overview for the recommended exponential backoff strategy.

Body (`application/json`): object

- `error` (string, example: `API token is at rate limit`)

Example shape (generated from the schema; placeholder values, not a real response):

```json
{
  "error": "API token is at rate limit"
}
```
