# Send feedback about the API.

`POST /feedback`

> Wheelhouse Revenue Management API. Web version: https://docs.usewheelhouse.com/rm/reference/rm-post-feedback · OpenAPI spec: https://docs.usewheelhouse.com/rm/openapi.yaml · Operation ID: `rmPostFeedback` · Tag: Feedback

Sends feedback about this API to the Wheelhouse team: something that failed, documentation that was unclear or wrong, an endpoint or field you needed and could not find, or something that worked well. Every item is read and triaged; nobody replies to it, so do not use it for account support.

Write the `message` so that someone without your context can act on it: what you tried, what happened, and what you expected. Send one item per issue. Leave out guest names, contact details and other personal data.

Read-only API keys may send feedback, and feedback calls are not billed. Each user can send up to 30 items per hour and 100 per day; more returns **429**.

## Request

`POST https://api.usewheelhouse.com/ss_api/v1/feedback`

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)

- `message` (string, required, max length: 4000): The feedback itself. At most 4000 characters.
- `category` (string, one of: `bug`, `confusing_docs`, `missing_capability`, `praise`, `other`, default: `other`): What kind of feedback this is. `bug`: something returned an error or a wrong result. `confusing_docs`: the documentation was unclear, incomplete or wrong. `missing_capability`: something you needed that the API cannot do. `praise`: something that worked well. `other`: anything else. Defaults to `other`.
- `endpoint` (string, max length: 255): The endpoint the feedback is about, such as `GET /listings/{listing_id}/price_recommendations`. Leave it out for feedback that is not about one endpoint, such as a request for something new. At most 255 characters.
- `listing_id` (string, max length: 100): The listing the feedback is about, if any, as you would pass it to other endpoints. At most 100 characters.

### Example request

```bash
curl -X POST 'https://api.usewheelhouse.com/ss_api/v1/feedback' \
  -H 'X-Integration-Api-Key: <your RM API key>' \
  -H 'Content-Type: application/json' \
  -d '{
  "message": "string"
}'
```

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

### 201

The feedback was received.

Body (`application/json`): object

- `id` (integer): Identifies this feedback item. Quote it if you refer to the item elsewhere.
- `category` (string): The category the feedback was stored under.
- `created_at` (string (date-time)): When the feedback was received.
- `note` (string): A confirmation to pass on to the person you are working for, including where to go for account support.

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

```json
{
  "id": 0,
  "category": "string",
  "created_at": "2026-01-01T00:00:00Z",
  "note": "string"
}
```

### 400

Invalid parameters, such as a missing or overlong `message` or an unknown `category`.

### 401

API key authorization failed.

### 429

Too much feedback from this user in the last hour or day, or the API key is at its rate limit.
