Spirit Cruises API
No API of its own; spiritcruises.com is a consumer storefront that redirects to the parent City Experiences brand. The parent's Anchor Operating System exposes a partner booking API at devshop.hornblower.com, but it is sold to tour operators and OTAs, not offered for Spirit Cruises.
Frequently asked questions
Spirit Cruises scores F on the API Report Card. No API of its own; spiritcruises.com is a consumer storefront that redirects to the parent City Experiences brand. The parent's Anchor Operating System exposes a partner booking API at devshop.hornblower.com, but it is sold to tour operators and OTAs, not offered for Spirit Cruises.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
Spirit Cruises is a U.S. dining and sightseeing cruise brand best known for the Spirit of Boston, Spirit of Philadelphia, Spirit of New York, Spirit of Norfolk, and Spirit of Washington DC vessels, which run lunch, brunch, dinner, holiday, and private-event cruises in major East Coast harbors.
Consumer travel and hospitality, specifically dining cruises, sightseeing cruises, private charters, weddings, corporate events, and holiday cruises. Consumers visit (or are redirected from) spiritcruises.com to browse and book dinner cruises, lunch cruises, themed holiday cruises (NYE, July 4th, Mother's Day, Thanksgiving), and private charters on Spirit vessels.
Low as a software/integration target.
Spirit Cruises legacy: 7+ namesake vessels operating in Boston, Philadelphia, New York/NJ, Norfolk, and DC-area harbors; historically part of Entertainment Cruises' ~2M-guest/year fleet.
Spirit Cruises traces back to 1978 in Norfolk, Virginia, and was operated for decades as part of Entertainment Cruises before being absorbed by Hornblower Group and consolidated into the City Cruises / City Experiences brand in 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.