The API Report CardAPI Index
City Sightseeing

City Sightseeing API

Hop-on Hop-off Bus Tours / Tours & Attractions Operator · citysightseeing.com

No first-party API. Reseller connectivity to City Sightseeing inventory runs through Prioticket's global marketplace and Ventrata's OCTO API per local operator. The franchise structure means availability and pricing are managed per city, with no single canonical surface across the brand.

Last verified: July 2026Hospitality & Travel
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceFAILNo first-party API. Ticketing connectivity runs through Prioticket's marketplace and Ventrata's OCTO API per operator.
AccessFAILResellers integrate with Prioticket or Ventrata for each operator; City Sightseeing itself offers no onboarding.
CoveragePOORAvailability, pricing, and refunds are managed per city by local operators on their own POS; no brand-wide surface exists.
AuthFAILNo OAuth registration or credentials exist at the brand level; authentication happens with third-party vendors.
Docs & DXFAILNo developer portal, docs, SDKs, webhooks, status page, or rate limits are published for the brand.
StabilityMIXED
Supergood: City Sightseeing isn't going to ship an API, so we did: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

City Sightseeing scores F on the API Report Card. No first-party API. Reseller connectivity to City Sightseeing inventory runs through Prioticket's global marketplace and Ventrata's OCTO API per local operator. The franchise structure means availability and pricing are managed per city, with no single canonical surface across the brand.

Tried to integrate with City Sightseeing?
SOURCES
No public developer documentation exists at citysightseeing.com or city-sightseeing.com, no developer portal, no API reference, no SDKs, no OAuth flow city-sightseeing.com
Reseller / OTA connectivity is routed through third-party platforms (Prioticket marketplace, Ventrata OCTO API) rather than a first-party City Sightseeing API, so partners are dependent on the vendor's roadmap and SLA, not on City Sightseeing prioticket.com
Franchise structure means availability, pricing, and refund-policy data are managed per-city by local operators on their chosen POS, so there is no single canonical API surface across the brand en.wikipedia.org
No published webhook, status page, rate limits, or developer support channel for City Sightseeing as a brand; integrators must work through Prioticket / Ventrata support docs.ventrata.com
Trustpilot reviewers report buses failing to arrive at scheduled stops, with customers waiting 45-60 minutes when frequency is advertised as 15-30 minutes (Lisbon, Rome, London cited) trustpilot.com
Customer-service contact is chat-only with no published phone number or email; multiple reviewers say chat tickets close without a refund being issued trustpilot.com
Refund denials reported even when cancellations were submitted within the advertised 24-hour free-cancellation window; 'flexible voucher valid 12 months' policies described as misleading trustpilot.com
Tripadvisor reviews of City Sightseeing London cite cancellation with no refund and no communication from the operator tripadvisor.com
Tripadvisor reviews of City Sightseeing Rome cite inability to use tickets after disruption with no refund offered tripadvisor.com
BBB complaints against City Sightseeing New York (franchisee) covering refund and service-quality disputes bbb.org
Lisbon reviewers report broken on-board audio jacks / non-working audio commentary points along the route trustpilot.com
Quality and service inconsistency across cities is structurally tied to the franchise model, each city is a separate local operator with its own staffing, fleet condition, and customer-service standards, so the central brand carries reputational risk it does not directly control en.wikipedia.org