# Get the estimated fee multiplier per stay date for a listing.

`GET /listings/{listing_id}/fee_impact_calendar`

> Wheelhouse Revenue Management API. Web version: https://docs.usewheelhouse.com/rm/reference/rm-get-fee-impact-calendar · OpenAPI spec: https://docs.usewheelhouse.com/rm/openapi.yaml · Operation ID: `rmGetFeeImpactCalendar` · Tag: Calendar

Returns a per-date fee multiplier derived from the listing's `fee_adjustments` preference (`total_fee_percentage`, see `GET /preferences/{listing_id}`). Multiply any nightly price by `fee_multiplier` to obtain the fee-inclusive price, for example before comparing it with neighborhood prices, which include fees.

When no fee adjustment is in effect, `fee_multiplier` is `1.0`. Pass `fallback=estimate` to have it estimated instead from the fees on the listing's recent reservations, the same estimate `auto_update` applies. Each entry's `source` says where the multiplier came from.

Currently the multiplier is uniform across all dates. The per-date shape is intentional — future releases will allow fee variation by date range or season, and the response format will remain compatible.

Defaults to today through the maximum calendar horizon (1.5 years) when `start_date` and `end_date` are omitted. The total date range may not exceed 3 years.

## Request

`GET https://api.usewheelhouse.com/ss_api/v1/listings/{listing_id}/fee_impact_calendar`

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 | First stay date to include (YYYY-MM-DD). Defaults to today. |
| `end_date` | string (date) | no | Last stay date to include (YYYY-MM-DD). Defaults to the maximum calendar horizon (1.5 years from today). The total range (`start_date` to `end_date`) may not exceed 3 years. |
| `fallback` | string | no | What to report when the listing has no fee adjustment in effect. `none` (the default) reports `1.0`. `estimate` estimates the multiplier from the fees on the listing's recent reservations, and still reports `1.0` when none of them carries fee data. (one of: `none`, `estimate`, default: `none`) |

### Example request

```bash
curl -X GET 'https://api.usewheelhouse.com/ss_api/v1/listings/{listing_id}/fee_impact_calendar?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

Array of fee multiplier entries ordered by stay date.

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

- `stay_date` (string (date)): The stay date.
- `fee_multiplier` (number): Multiply a nightly price by this value to get the fee-inclusive price. `1.0` means no fee is applied; `1.15` means a 15% estimated fee.
- `source` (string, one of: `setting`, `estimate`, `none`): Where `fee_multiplier` came from: `setting` is the listing's fee adjustment, `estimate` is estimated from the listing's recent reservations (only with `fallback=estimate`), and `none` means neither applies, so the multiplier is `1.0`.

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

```json
[
  {
    "stay_date": "2026-01-01",
    "fee_multiplier": 0,
    "source": "setting"
  }
]
```

### 400

Date range exceeds the 3-year maximum, or `fallback` is not one of the listed values.

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