Knowledge BaseKnowledge Base

Setting Up the Track PMS Connector

Connect Track PMS into Wazzi for properties, reservations, owners, contacts, and CRM data via MCP.

April 25, 2026
5 min read

Path: Connectors → Track PMS → Configuration

What this connector does

The Track PMS connector exposes your vacation rental management data — units (properties), reservations, owners, contacts (guests), companies, CRM tasks/leads, reviews, and rates — to your team's AI assistants via MCP. Property managers use it to answer "what's the availability for this weekend?" or "show me the contact record for that recent reservation" without digging through Track.

It also feeds Wazzi's Data Sources for any Centers products that consume Track data (Operations Center, Portfolio Center).

Wazzi authenticates using HTTP Basic auth over the channel manager API — your Track-issued channel key as the username and channel secret as the password.

Before you start — getting your Track credentials

You'll need:

  • A Track PMS account (TRACK Pulse, TRACK Hospitality Software).
  • Admin access to your Track tenant.
  • Your Track customer URL — the hostname for your tenant, typically https://<your-company>.trackhs.com/api.
  1. Sign in to Track and open Channel Manager from the main menu.
  2. Locate the API credentials section. Track typically issues these via support — file a ticket if you don't see them, asking for "channel key + secret for third-party integration with Wazzi MCP."
  3. Copy three values:
    • API URL — your tenant base URL (e.g., https://acme.trackhs.com/api).
    • Channel Key — your tenant-specific username.
    • Channel Secret — pairs with the key. Treat as a password.

Reference: Track's developer portal is at developer.trackhs.com. If you can't access it, your Track customer success rep can grant credentials.

Heads up — rate limits. Track allows 10,000 requests per 5 minutes per IP. Generous for typical usage, but heavy backfills can hit the cap. Wazzi paces sync requests automatically; direct AI tool calls are subject to the same limit.

What this connector unlocks for your team

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

  • "List units at the Aspen node."
  • "Show me the latest reservations in the Lake Tahoe portfolio."
  • "Pull up the contact record for guest@example.com."
  • "Find owner statements for property ID 12345 last quarter."
  • "Get availability and a quote for the Beach House next weekend."

The exact set of available actions depends on which MCP toggles you've flipped on for the user's group — see Managing Permissions.

Steps — configuring Track in Wazzi

1. From the Connectors catalog, click Configure on the Track PMS tile.

You'll land on Track's Configuration tab:

Track PMS connector Configuration tab

2. Fill in the three fields.

  • API URL — your customer-specific base URL (e.g., https://acme.trackhs.com/api).
  • API Key — your channel manager username (Track may call this "channel key").
  • API Secret — your channel manager password ("channel secret"). Encrypted at rest.

3. Click Test Connection.

Wazzi calls a lightweight Track endpoint (typically GET /pms/units with page_size=1) to verify the credentials. Success returns a 200 with the first record.

4. Click Save Configuration.

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

Troubleshooting

  • "Test Connection failed: 401 Unauthorized." Channel key or secret is wrong. Re-copy from Track Channel Manager. Pasted whitespace is the most common cause.
  • "Test Connection failed: 403 Forbidden." Credentials are valid but the channel doesn't have access to the endpoint. Contact Track support and ask them to extend the channel's API permissions.
  • "Test Connection failed: 404 Not Found" or DNS errors. Customer URL is wrong. Verify the hostname (e.g., https://acme.trackhs.com/api, including the /api suffix) by signing into Track and checking the URL.
  • Rate-limit errors. You're past 10,000 req / 5 min. Pace AI prompts; Wazzi-driven scheduled syncs (Data Sources) auto-back-off.
  • The connector worked yesterday and fails today. Track rotated the channel manager creds. Get fresh ones from your Track contact and update Wazzi.

Best practices

  • Use a dedicated channel manager user. Track issues channel manager credentials per integration — make sure yours is named clearly (e.g., "Wazzi MCP") so it's easy to revoke later.
  • Document your Track CSM contact. Track support handles credential issuance and rotation; keep their contact info handy.
  • Set a quarterly rotation reminder. Track credentials don't expire automatically.
  • Wire Track into Data Sources. Track is a strong fit for Wazzi's Operations Center and Portfolio Center data sources. See Configuring Data Sources.

Frequently asked questions

Does Wazzi store the channel secret in plaintext?
No. Encrypted at rest with per-org keys; decrypted only at request time.

Can I connect multiple Track tenants?
Track is a single-instance connector. Most teams have a single tenant — pick that one.

Will this connector write to Track?
The connector includes admin tools for units, reservations, owners, CRM, and rates / taxes. Track's API supports both read and write; Wazzi exposes both surfaces. Permissions decide which the AI can invoke for any given user.

Why "channel key" instead of "API key"?
Track historically rolled API access through their channel-manager interface. The terminology stuck. Functionally it's HTTP Basic auth.

What's next

Was this article helpful?