; }; OpenCX supports **multiple FareHarbor connections per organization** — one per location, brand, or currency account. Each connection has its own API keys and its own AI action toggles. ## Prerequisites You need an **App Key** and a **User Key** issued by FareHarbor. These authenticate every request OpenCX makes to the FareHarbor API on your behalf. Contact FareHarbor to register as an API partner if you do not already have keys. If you work with FareHarbor companies in different currencies (USD, NZD, EUR, etc.), you will have a separate **User Key for each currency**. Add one connection per currency — the AI will route each booking to the right connection automatically. ## Setup In your [OpenCX dashboard](https://platform.open.cx/settings/integrations), go to **Settings → Add-ons** and select **FareHarbor**. Click **Add Connection**. If you already have connections configured, they are listed here — you can add more by clicking the button again. Enter a **connection name** that reflects what this connection is — for example `Downtown Location`, `USD Account`, or `RealNZ`. The name is what your AI agent uses to disambiguate between connections during customer conversations, so pick something meaningful. Pick names your **customers** would recognize, not internal codes. If a customer asks about a specific brand or region, the AI can match the request to the right connection without asking. Toggle **Sandbox Mode** on for testing. This points the connection at FareHarbor's demo environment — no real bookings, no real charges. Paste your **App Key** and **User Key**. OpenCX validates both keys immediately by calling the FareHarbor API to list your affiliated companies. If validation fails, double-check that the keys are correct and that the User Key matches the currency of at least one affiliated company. After key validation succeeds, a dropdown appears with the companies affiliated with this User Key. Pick the company you want this connection to book for. If there is only one, it is selected automatically. You can also leave this as **Auto-detect** — the AI will use the first company returned by the FareHarbor API for this connection. OpenCX runs a final validation and saves the connection. The new connection appears in the list and is ready to use immediately. ## Managing connections Each connection has its own settings panel, reached by clicking it in the connection list: * **AI actions** — eight toggleable capabilities (list items, check availability, validate booking, create booking, get booking, cancel booking, generate payment link, send payment link via SMS). Each connection has its own toggles, so you can allow bookings on one location while keeping another read-only. * **Disconnect** — removes just that connection. Other connections remain active. ## How the AI picks the right connection When you have more than one connection, every FareHarbor tool call the AI makes includes a **location** parameter — which connection to use. The AI resolves this automatically whenever it can: * If the customer mentions a specific company, tour, or region that maps to one connection, the AI uses it without asking. * If the request is ambiguous (e.g. "what tours do you have?"), the AI asks the customer which location or brand they are interested in. With a **single connection**, there is no `location` parameter and no disambiguation — behavior is identical to a single-connection setup. ## Disconnecting To remove a single connection, open it from the connection list and click **Disconnect**. This removes: * The stored API keys for that connection * The AI action settings for that connection Other connections, and your FareHarbor account itself, are not affected. *** ## Related Documentation Connection failures, missing availability, SMS delivery. How each AI action works day-to-day. Capabilities, supported channels, and how it all fits together. Booking experience in chat widget, WhatsApp, and SMS.