# Delete multiple custom rate ranges for a listing in bulk.

`DELETE /listings/{listing_id}/bulk_custom_rates`

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

Removes custom rates for multiple date ranges in a single request. Partially successful requests return status `207`; fully failed requests return `424`.

## Request

`DELETE https://api.usewheelhouse.com/ss_api/v1/listings/{listing_id}/bulk_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`. |

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

- `channel` (string): 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).
- `delete_ranges` (array of object, required)
  - `start_date` (string (date), required): The start date of the range to delete (YYYY-MM-DD). This date is inclusive.
  - `end_date` (string (date), required): 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}/bulk_custom_rates' \
  -H 'X-Integration-Api-Key: <your RM API key>' \
  -H 'Content-Type: application/json' \
  -d '{
  "delete_ranges": [
    {
      "start_date": "2026-01-01",
      "end_date": "2026-01-01"
    }
  ]
}'
```

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

All ranges deleted successfully. No content is returned.

### 207

Some ranges deleted and some failed.

Body (`application/json`): object

- `errors` (array of object `custom_rate_error`)
  - Fields: see `custom_rate_error` under Schemas.

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

```json
{
  "errors": [
    {
      "start_date": "2026-01-01",
      "end_date": "2026-01-01",
      "http_code": 0,
      "message": "string"
    }
  ]
}
```

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

### 424

All ranges failed to delete.

Body: same as `207` above.

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

## Schemas

Shared by more than one field above.

### `custom_rate_error`

Type: object `custom_rate_error`

An error that occurred when processing a custom rate.

- `start_date` (string (date))
- `end_date` (string (date))
- `http_code` (integer)
- `message` (string)
