FareHarbor
FareHarbor provides online booking software for tours, activities, rentals, and attractions, enabling businesses to manage reservations, payments, and customer experiences through a scalable, cloud‑based platform. The solution supports multi‑channel sales, staff management, reporting, and integrations with partners, aiming to simplify operations for tour operators and activity providers worldwide.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles FareHarbor the way a machine reads it — 22 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — FareHarbor scores 42.1/100 (developing), with a separate agent-readiness read of 22/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
the company publishes no developer documentation host and no machine-readable contract on its own domain
This is an honest zero, not a gap in our research. FareHarbor does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://api.fareharbor.com/mcp→ HTTP 403https://fareharbor.com/mcp→ HTTP 403https://help.fareharbor.com/mcp→ HTTP 401https://fareharbor.com/→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from FareHarbor's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fareharbor/"
title="FareHarbor on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fareharbor.svg"
alt="FareHarbor Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/fareharbor/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fareharbor/"
title="FareHarbor on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fareharbor/card.svg"
alt="FareHarbor Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile FareHarbor
Each block below is one kind of artifact we hold for FareHarbor. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
FareHarbor Integration Center
FareHarbor Integration Center API
FareHarbor Availabilities Endpoints API
The `/availabilities` endpoint is used to retrieve all bookable availabilities for a single item within a specified date or date range. The request pulls availability data from ...
FareHarbor Bookings Endpoints API
The bookings endpoints in the FareHarbor API provide comprehensive functionalities for managing reservations efficiently. These endpoints enable developers and business owners t...
FareHarbor Checkin Endpoints API
The check-in endpoints in the FareHarbor API provide essential capabilities for managing the check-in processes efficiently and seamlessly. These endpoints are crucial for busin...
FareHarbor Company Endpoints API
The Company endpoints in the FareHarbor API provide robust functionalities for accessing and managing information related to companies that offer tours and activities. These end...
FareHarbor Crew Members Endpoints API
The Crew Members endpoints in the FareHarbor API provide comprehensive functionality for managing crew assignments on availabilities. These endpoints allow you to assign, update...
FareHarbor Items Endpoints API
The Items endpoints in the FareHarbor API provide comprehensive access to detailed information about the various activities and services offered by a company. These endpoints ar...
FareHarbor Lodging Endpoints API
With our `/lodgings` endpoints our API Partners are able to retrieve our charters’ lodging options, both on a dashboard level as well as on the availability level, and offer the...
FareHarbor Ping API
The Ping API from FareHarbor — 1 operation(s) for ping.
FareHarbor Roles Endpoints API
The Roles endpoints provide access to role definitions within companies, enabling structured crew member assignments with specific responsibilities and permissions.
FareHarbor Users Endpoints API
The Users endpoints provide access to user information within the context of company operations, specifically for crew management purposes.
Scroll within the panel for all 11 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Fareharbor Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
FareHarbor API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AVAILABILITY_RESPONSE_JSON_SCHEMA
JSON SCHEMABOOKING_RESPONSE_JSON_SCHEMA
JSON SCHEMABOOKING_WITH_PAYMENTS_RESPONSE_JSON_SCHEMA
JSON SCHEMAITEM_RESPONSE_JSON_SCHEMA
JSON SCHEMAITEMS_RESPONSE_JSON_SCHEMA
JSON SCHEMASecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for FareHarbor — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 2
Status, limits, changes, and where to get help
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/fareharbor · machine-readable index on apis.io
This is an independent, third-party profile of FareHarbor, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.