Hornblower API
The Anchor Operating System, Hornblower's technology arm, documents a booking API at devshop.hornblower.com: tours, availability, reserve, book, amend, and cancel. Auth is HTTP Basic with a token and a sandbox token is published. It targets OTAs and resellers; hornblower.com itself exposes none.
Frequently asked questions
Hornblower scores A on the API Report Card. The Anchor Operating System, Hornblower's technology arm, documents a booking API at devshop.hornblower.com: tours, availability, reserve, book, amend, and cancel. Auth is HTTP Basic with a token and a sandbox token is published. It targets OTAs and resellers; hornblower.com itself exposes none.
Hornblower has a workable official integration path. Most engineering teams can build against it directly. Open API: self-serve, documented, with SDKs
Hornblower is a cruise, tours, and experiences operator that runs branded sightseeing, dining, and ferry cruises across North America and Europe.
Hornblower itself is a hospitality/travel experiences brand serving end consumers (tourists, wedding/event planners, school groups). Consumers visit hornblower.com / cityexperiences.com to browse and book sightseeing cruises, dinner cruises, ferries, and attraction tickets. Corporate clients book private charters and event vessels.
Low as a software platform. As a consumer cruise brand, Hornblower / City Experiences is well known in major US cruise/tourism markets (NYC, SF, San Diego, Chicago, DC, Niagara). Hornblower Group reports serving 50M+ guests/year across its operations.
Hornblower Group: 50M+ guests served annually, operates in 110+ cities across 9 countries. Anchor Operating System has processed $1B+ in transactions, sold 70M+ tickets, claims 92% client retention, and operates in 15+ countries with 12+ OTA/payment integrations.
Hornblower Yachts was founded in 1980 in San Diego. The group has grown via acquisitions (Statue Cruises, Niagara Cruises, Walks, Devour, City Experiences brand 2021).
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.