Setting Up the Wheelhouse Connector

Path: Connectors → Wheelhouse → Configuration

What this connector does

Wheelhouse is a revenue-management platform for short-term rentals — dynamic pricing, occupancy forecasting, and market benchmarking. The Wheelhouse connector exposes that surface to Wazzi as MCP tools so your team's AI assistants can pull nightly rates, adjust pricing preferences, override rates for specific dates, and read live pricing recommendations without leaving the chat.

Wazzi authenticates with a single Wheelhouse RM API key sent as the X-Integration-Api-Key header. The older two-header (X-User-API-Key) scheme has been retired by Wheelhouse — you only need one key.

The Wazzi connector exposes 25+ tools grouped by domain:

• Listings (7 tools) — list all listings, get one, pull KPIs, flags, tags (read/write), and the pricing tier.
• Pricing calendar (2 tools) — read the day-by-day rate calendar and Wheelhouse's live recommendations.
• Custom rates (4 tools) — set / bulk-set / delete / bulk-delete manual rate overrides.
• Reservations (1 tool) — list reservations by date range and status.
• Preferences (pricing strategy) (10 tools) — read, batch-read, changelog, preview, per-listing update, bulk update, copy across listings, update a single setting, plus long-term-discount config.
• Discovery (1 tool) — get_base_price_recommendation to seed a new listing's starting rate.

Before you start — getting your API key

You'll need:

• A Wheelhouse account on a plan that includes API access (most enterprise / RM tiers).
• Admin permission on that account so you can generate an Integration API key.

1. Sign in to app.usewheelhouse.com.
2. Navigate to Account Settings → Integrations → API.
3. Generate a new Integration API Key, or copy your existing one. Treat the key like a password — it grants full read/write access to every listing on the account.

Reference: Wheelhouse's API reference lives at api.usewheelhouse.com/wheelhouse_rm_api. Base URL is fixed at https://api.usewheelhouse.com/ss_api/v1.

What this connector unlocks for your team

Once configured, members with the right MCP permissions can ask Claude / ChatGPT / Cursor things like:

• "Show me the nightly rate calendar for listing X for the next 60 days."
• "What's Wheelhouse recommending for the July 4th weekend across our beach portfolio?"
• "Set a $650/night floor on listing X from Dec 20 to Jan 2."
• "Copy the pricing preferences from listing X to every other 3-bedroom unit in the same market."
• "Which listings triggered a Wheelhouse flag in the last 24 hours?"
• "Preview what a 10-point aggressiveness bump would do to next weekend's rates before I apply it."
• "Pull the KPI dashboard for listing X — occupancy, ADR, RevPAR, pacing."

The exact set of available actions depends on (a) the plan tier your Wheelhouse account is on and (b) which MCP toggles are flipped on for the user's group in Wazzi — see Managing Permissions.

Steps — configuring Wheelhouse in Wazzi

1. From the Connectors catalog, click Configure on the Wheelhouse tile.

You'll land on Wheelhouse's Configuration tab:

2. Fill in the API Key field.

• API Key — the Integration API key you copied from Wheelhouse's Account Settings → Integrations → API. Stored encrypted at rest in Wazzi.

3. Click Test Connection.

Wazzi calls a lightweight Wheelhouse endpoint on your behalf. On success the health check reports "Connected" along with the number of listings visible to the key.

4. Click Save Configuration.

Wheelhouse moves to the Active section of the catalog and the dot turns green.

Troubleshooting

• "401 Unauthorized" or "403 Forbidden" on Test Connection. The API key is wrong or has been revoked. Most common cause: trailing whitespace when pasting. Re-copy from Wheelhouse's Integrations → API page and try again. If still failing, regenerate the key.
• "X-User-API-Key required" errors. That's the retired auth scheme; you're seeing it because a stale header is going out. The current connector uses only X-Integration-Api-Key — if you see this error, contact Wazzi support so we can double-check no old header is being injected.
• Empty listings on get_listings. The API key belongs to a Wheelhouse account with no assigned listings, or every listing is archived. Verify the key's account in Wheelhouse's UI.
• set_custom_rate accepted but the rate isn't visible in the UI. Wheelhouse pushes custom rates asynchronously to the connected PMS. The value shows in get_price_calendar immediately but may take up to an hour to appear in Streamline / OwnerRez / etc.
• update_preferences_bulk fails with "listing not found". One of the listing_ids in the payload doesn't belong to your account. Run get_listings first to gather valid ids.

Best practices

• Preview before you apply. preview_preferences shows what a preference change would do to future rates without committing. Use it before every bulk update.
• Keep custom rates surgical. Wheelhouse's recommendations are typically better than a static floor / ceiling — reserve set_custom_rate for holiday premiums, event-driven pricing, and known constraints.
• Rotate the API key periodically. Regenerate in Wheelhouse's Integrations → API tab every quarter and update Wazzi. Old keys remain valid until you explicitly revoke them.
• Restrict who can invoke write tools. set_bulk_custom_rates, update_preferences_bulk, and copy_preferences can change pricing across your entire portfolio in one call. Only grant those permissions to revenue-management staff — see Managing Permissions.
• Cache listing ids per session. Wheelhouse listing ids are stable across API calls — pull them once at the start of a chat and reuse rather than round-tripping get_listings repeatedly.

Frequently asked questions

Does Wazzi store my API key in plaintext?
No. The key is encrypted at rest with per-org keys and only decrypted at the moment an outbound call is made.

Can I connect multiple Wheelhouse accounts?
Wheelhouse is a single-instance connector today. If you need to expose more than one Wheelhouse account from the same Wazzi org, file a feature request for multi-instance support.

What's the difference between set_custom_rate and update_preference_setting?
set_custom_rate forces a specific nightly rate on a specific date, overriding Wheelhouse entirely. update_preference_setting tweaks the parameters Wheelhouse uses to compute rates (aggressiveness, min stay, base price, etc.) — it stays dynamic. Use custom rates sparingly; use preferences for ongoing strategy.

What if the PMS goes out of sync with what I set here?
Wheelhouse pushes rates to your connected PMS on its own schedule (typically hourly). If a manual PMS edit lands after a Wheelhouse push, the next Wheelhouse push will overwrite it. Keep pricing decisions in Wheelhouse to avoid seesawing.

What's next

• Restrict who in your org can invoke Wheelhouse actions: Managing Permissions.
• Wire Wheelhouse into your AI tool: Connecting Claude or Connecting ChatGPT.
• Browse other connectors: Browsing the Connectors Catalog.