City Experiences API
The Anchor API at devshop.hornblower.com is a documented REST plus GraphQL surface for tour catalog, availability, reservations, and payments. Docs are public, but production credentials require completing a certification booking flow, and the broader Travel Partner program is sales gated.
Frequently asked questions
City Experiences scores A on the API Report Card. The Anchor API at devshop.hornblower.com is a documented REST plus GraphQL surface for tour catalog, availability, reservations, and payments. Docs are public, but production credentials require completing a certification booking flow, and the broader Travel Partner program is sales gated.
City Experiences has a workable official integration path. Most engineering teams can build against it directly. Open API: self-serve, documented, with SDKs
City Experiences is the consumer brand for Hornblower Group's portfolio of water- and land-based tour, cruise, ferry, and attraction businesses.
Vertical: misc, tour operator, cruise operator, urban ferry, iconic attractions. Closest canonical Supergood neighbors are POS/Hospitality and Travel & Expense, but neither fits cleanly. A consumer goes to cityexperiences.com, searches a city, picks an experience (e.g., 'Statue of Liberty Reserve Ticket' or 'Niagara Falls Voyage to the Falls Boat Tour' or 'NYC Holiday Lights Dinner Cruise'), selects a date and timeslot, and checks out, the booking is processed by Anchor on the back end.
4/10 as a B2B platform / system of record.
Yes, for a tour or attraction operator running on Anchor (the platform underlying cityexperiences.com), the system is the system of record for tour and timeslot inventory and capacity, dynamic pricing and yield rules, reservation and booking records (with 15-minute holds), guest CRM (name, contact, payment methods on file, prior trips, membership tier, accessibility flags), gift card balances, membership entitlements, F&B / merch / retail POS transactions, pick-up logistics, vessel and crew scheduling for cruise operations, check-in / boarding pass data, EFTPOS payment terminal data, and full financial settlement records.
Hornblower's earliest entity (Hornblower Cruises & Events) was founded in 1980 in San Francisco.
Anchor API production access is gated behind a manual certification process, developers must demonstrate successful end-to-end booking flow (retrieve → availability → reserve → confirm) before getting prod credentials, slowing time-to-launch for new integrators. Travel Partner program at cityexperiences.com/travel-partners exposes 'API Integrations with Key Partners' but does not publish endpoint docs, auth model, or rate limits on the public page, partnership is sales-gated via a registration form. Full sourced list under Sources below.
Common alternatives include Viator (TripAdvisor), GetYourGuide, Klook, Tiqets, Big Bus Tours, CitySightseeing. Graded alternatives appear under "More from the report card" below.
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.