# Delete custom rates for a date range on a listing.

`DELETE /listings/{listing_id}/custom_rates`

> Wheelhouse Revenue Management API. Web version: https://docs.usewheelhouse.com/rm/reference/rm-delete-custom-rate · OpenAPI spec: https://docs.usewheelhouse.com/rm/openapi.yaml · Operation ID: `rmDeleteCustomRate` · Tag: Custom Rates

Removes all custom rates overlapping the specified date range. If a custom rate period
extends beyond the deleted range on one side only, it is truncated to the non-overlapping
portion. If the deleted range falls in the middle of an existing rate period, that period
is split into two — one before and one after the deleted range. The deleted dates revert
to the Wheelhouse recommended price.

## Request

`DELETE https://api.usewheelhouse.com/ss_api/v1/listings/{listing_id}/custom_rates`

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`.

### 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) | yes | The start date of the range to delete (YYYY-MM-DD). This date is inclusive. |
| `end_date` | string (date) | yes | The end date of the range to delete (YYYY-MM-DD). This date is inclusive. |

### Example request

```bash
curl -X DELETE 'https://api.usewheelhouse.com/ss_api/v1/listings/{listing_id}/custom_rates?channel=<channel>&start_date=<start_date>&end_date=<end_date>' \
  -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

### 204

Custom rates deleted successfully. No content is returned.

### 400

Validation failed (e.g. start_date > end_date).

### 401

API key authorization failed.

### 403

Listing authorization failed, or the API key is read-only and may not be used with DELETE.

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