The API Report CardAPI Index
FareHarbor

FareHarbor API

Tours, Activities & Attractions Booking / Reservation Management · fareharbor.com

FareHarbor documents an External API at developer.fareharbor.com covering bookings, availabilities, items, and customers. No self-serve signup exists; keys are provisioned manually after approval into the Affiliate or Software Partner program. Webhooks cover only Booking and Item events.

Last verified: July 2026Hospitality & Travel
API GRADE
D+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODA documented External API at developer.fareharbor.com, plus a separate Distribution Network for OTA channels.
AccessPOORNo self-serve signup; you email partnerships, get approved as an Affiliate or Software Partner, and wait for manual keys.
CoveragePOORWebhooks fire only for Booking and Item events; customer, payment, refund, and availability changes must be polled.
AuthGOODTwo scoped keys: X-FareHarbor-API-App identifies the integration, X-FareHarbor-API-User defines permissions.
Docs & DXPOORDocs are sparse; a GitHub repo and a community Postman collection fill gaps in the official YAML spec.
StabilityMIXEDRate limits and SLA terms are unpublished; integrators discover throttling empirically and escalate via partner managers.
MORE FROM THE REPORT CARD
Supergood: FareHarbor has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

FareHarbor scores D+ on the API Report Card. FareHarbor documents an External API at developer.fareharbor.com covering bookings, availabilities, items, and customers. No self-serve signup exists; keys are provisioned manually after approval into the Affiliate or Software Partner program. Webhooks cover only Booking and Item events.

Tried to integrate with FareHarbor?
SOURCES
No public/self-serve developer signup - integrators must email FareHarbor partnerships and be approved into the Software Partner or Affiliate program before receiving X-FareHarbor-API-App and X-FareHarbor-API-User credentials. developer.fareharbor.com
Two-header authentication scheme (X-FareHarbor-API-App + X-FareHarbor-API-User) is non-standard and forces every consuming app to roll a bespoke auth integration vs. dropping in an OAuth client. rollout.com
Many analytics, marketing pixel, and tracking integrations cannot be self-installed by operators - they require FareHarbor Support to set up server-side on the backend, creating a support bottleneck for ISVs and agencies. help.fareharbor.com
Documentation is sparse compared to peers like Stripe/Square - GitHub docs repo and a community-maintained Postman collection fill gaps in the official YAML spec. github.com
Webhook surface limited to Booking and Item events; integrators wanting fine-grained customer, payment, refund, or availability change events have to poll. developer.fareharbor.com
Rate limits and SLA terms are not publicly published; integrators discover throttling behavior empirically and must escalate via Partner Manager. postman.com
Distribution Network (OTA channel) is a separate integration path from the External API, with its own approval and onboarding flow - duplicative work for partners who want both ISV and reseller paths. fareharbor.com
6% booking fee is among the highest in the category; small operators object to either absorbing the cost or passing it to guests. Reports allege FareHarbor rounds up booking totals and keeps the difference. bookeo.com
Slow Lightframe checkout - one operator reports a 14-second 'spinning wheel of death' during the booking process, cited as causing a 25% drop in sales. trustpilot.com
Confusing/dated dashboard UX; operators describe it as 'convoluted' and unintuitive, particularly users coming from modern SaaS. capterra.com
Limited self-service customization - most non-trivial changes (analytics integration, booking flow tweaks, pixel installs) require contacting FareHarbor Support to perform on the backend. help.fareharbor.com
Contract lock-in concerns and difficulty migrating off the platform once historical bookings, customer records, and waivers are inside. g2.com
Per Booking Holdings ownership, channel distribution favors BKNG-owned properties; operators report pressure to enable Booking.com Experiences distribution. squadtrip.com
Customer service responsiveness inconsistent at scale despite advertised 24/7 support; complaints of slow ticket resolution as the customer base grew post-BKNG acquisition. fareharbor.pissedconsumer.com