integrate an ota-style booking channel with an attraction's anchor operating system inventory via the anchor api
domain: devshop.hornblower.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
disambiguate the platform first: Anchor Operating System, LLC is a Hornblower Group subsidiary providing attractions ticketing/POS — distinct from unrelated products that also use the 'Anchor' name
find Anchor Operating System's API reference, hosted at devshop.hornblower.com/docs, which documents an OTA-style booking connector flow under paths such as /api/gyg/1/...
send HTTPS requests with JSON payloads and the Content-Type header set, authenticating via an Authorization header, per the devshop.hornblower.com/docs reference
to pass integration approval, execute the full booking lifecycle in test: create a booking, amend it, then cancel it by booking reference or reservation reference
email Anchor's API team to confirm the test booking and wait for their review and confirmation of the integration before requesting production credentials
retrieve bookings/tickets by booking reference, reflecting the GetYourGuide-style connectivity pattern that other channel integrations follow
Known gotchas
Anchor's marketing site advertises an API but does not itself publish reference docs or link to them from its nav — the real spec lives on a separate Hornblower-operated subdomain that must be found independently
the API always returns HTTP 200 as long as the response contains an expected payload — errors are communicated via payload-embedded codes rather than HTTP status codes, a common source of integration bugs
production access is gated behind manual review: a full create/amend/cancel booking cycle must be demonstrated and confirmed by email with Anchor's API team before production credentials are issued — not self-serve
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?