# Get the changelog of all changes to a listing.

`GET /preferences/{listing_id}/changelog`

> Wheelhouse Revenue Management API. Web version: https://docs.usewheelhouse.com/rm/reference/rm-get-preferences-changelog · OpenAPI spec: https://docs.usewheelhouse.com/rm/openapi.yaml · Operation ID: `rmGetPreferencesChangelog` · Tag: Listing Preferences

Returns a list of recent change events for the listing, most recent first. Despite sitting under `/preferences`, the changelog is not limited to preference changes: it is the single history of everything recorded against the listing. It covers changes to the pricing settings, prices posted to the channel and any post or calendar sync that failed, custom rates added, split or removed, a change of pricing engine, and reservations imported for the listing. Read `event` on each entry to tell them apart. Custom rate history is therefore read from here rather than from the Custom Rates endpoints, which report the rates currently in force.

## Request

`GET https://api.usewheelhouse.com/ss_api/v1/preferences/{listing_id}/changelog`

Authentication: send your RM API key in the `X-Integration-Api-Key` header (see https://docs.usewheelhouse.com/rm/authentication.md). Read-only keys can call this endpoint.

### Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `listing_id` | string | yes | The channel's unique listing identifier, or the Wheelhouse listing ID when `channel` is `wheelhouse`. |

### Query parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `channel` | string | yes | Channel name the listing is on (the `channel` field of the [/listings](https://docs.usewheelhouse.com/rm/reference/rm-get-listings.md) response), or the literal `wheelhouse` to read `listing_id` as a Wheelhouse listing ID instead. See [Identifying Listings](https://docs.usewheelhouse.com/rm/concepts/listings.md). |
| `start_date` | string (date) | no | Start of the date range to retrieve changes for. Defaults to 30 days ago. A request returns at most one year, so a `start_date` more than a year before `end_date` is moved forward to one year before `end_date` (no error is returned). To read older history, move `end_date` back as well, e.g. `start_date=2024-01-01&end_date=2025-01-01`, then `start_date=2023-01-01&end_date=2024-01-01`. |
| `end_date` | string (date) | no | End of the date range to retrieve changes for. Defaults to tomorrow. Clamped to the range [`start_date` + 1 day, tomorrow] (no error is returned). |
| `event` | array of string | no | Return only events of these types (the `event` field of each entry). Defaults to every type. Leaving out `Prices posted` drops the automatic price posts, which outnumber everything else on a listing that posts daily, e.g. `?event[]=Settings changed&event[]=Custom rates` for setting and custom rate changes only. Send more than one comma-separated (`?event=Settings changed,Custom rates`) or in brackets; a key repeated without brackets keeps only its last value. (each item one of: `Prices posted`, `Calendar synced`, `Settings changed`, `Custom rates`, `Reservations imported`) |

### Example request

```bash
curl -X GET 'https://api.usewheelhouse.com/ss_api/v1/preferences/{listing_id}/changelog?channel=<channel>' \
  -H 'X-Integration-Api-Key: <your RM API key>'
```

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

List of changelog events.

Body (`application/json`): object

- `events` (array of object)
  - `time` (string (date-time)): When the change occurred (ISO-8601).
  - `source` (string): Who triggered the change. Known values: `'Wheelhouse'` (system-generated — auto price posting, internal adjustments, migrations); `'User'` or `'User <name>'` (user-initiated); `'API'` (updated via API); `'Customer Support'` (Wheelhouse support staff); `'Wheelhouse team'` or `'Wheelhouse team <name>'` (reservation imports).
  - `event` (string): The type of event. Known values: `'Prices posted'`, `'Calendar synced'`, `'Settings changed'`, `'Custom rates'`, `'Reservations imported'`.
  - `status` (string): The outcome of the event. Known values: `'success'`, `'warning'` (partial success: e.g. some prices posted, but the channel rejected some dates; `msg` says what to fix), `'error'`.
  - `msg` (string): A human-readable description of the change.

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

```json
{
  "events": [
    {
      "time": "2026-01-01T00:00:00Z",
      "source": "string",
      "event": "string",
      "status": "string",
      "msg": "string"
    }
  ]
}
```

### 401

API key authorization failed.

### 403

Listing authorization failed.

### 404

Listing not found.

### 406

The listing is inactive. See the **Inactive Listings** section in the overview.

Body (`application/json`): object

- `error` (string, example: `Listing '12345' is inactive`)

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

```json
{
  "error": "Listing '12345' is inactive"
}
```

### 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"
}
```
