Trafalgar API
The TravelCorp API V4 at api.ttc.com serves Trafalgar inventory over REST/JSON: brands, tours, availability, card payments, and agent SSO. Docs are partly public, but access takes a manual request review, and the sandbox sits behind the same gate.
Frequently asked questions
Trafalgar scores B+ on the API Report Card. The TravelCorp API V4 at api.ttc.com serves Trafalgar inventory over REST/JSON: brands, tours, availability, card payments, and agent SSO. Docs are partly public, but access takes a manual request review, and the sandbox sits behind the same gate.
Trafalgar has a workable official integration path. Most engineering teams can build against it directly. Solid API with minor gaps
Trafalgar is the flagship guided escorted-tour brand within The Travel Corporation (TTC) portfolio, operating alongside CostSaver, Insight Vacations, Luxury Gold, Contiki, and Brendan Vacations.
Consumer leisure travel / guided escorted tour operator. Consumers browse itineraries on trafalgar.com (or localized en-au, en-gb, en-ca, en-za, en-ie variants), request brochures or quotes, and either book direct (deposit + balance, flexible 90-day cancellation, no change fees) or hand off to a travel advisor.
Medium-high as a consumer travel brand, low as a 'platform.' Trafalgar is one of the most recognized escorted-tour brands globally (5M+ lifetime guests, 4.6/5 on Feefo across 150K+ verified reviews, 4+/5 on Trustpilot, 102,000+ reviews and 472 trips listed on Travelstride, regular industry-awards holder) and is the TTC flagship that anchors the wider portfolio.
For Trafalgar / TTC internally: guest PII (name, DOB, passport, dietary/medical needs, mobility status, emergency contacts), payment records, deposit/balance ledgers, departure manifests, coach/hotel inventory, MAKE TRAVEL MATTER and optional-excursion selections, travel-advisor commission records, loyalty-program records, and trip-registration data.
Mature consumer brand - 79 years of continuous operation as of 2026 (founded 1947), and the anchor of the multi-brand TTC portfolio.
No public developer complaints are surfaced via search - consistent with a small, manually-vetted partner cohort using the API. The TravelCorp API V4 documentation portal is partly publicly readable but request-access is gated; any 'documentation sparse,' 'access-request slow,' or auth-quirk chatter would only appear in private partner channels. No GitHub issues, Stack Overflow tags, or developer-forum threads were found for `travelcorp-api`, `ttc-api`, or Trafalgar-specific API usage. Sandbox / sandbox parity is not publicly documented (sandbox.api.ttc.com requires the same access request as production); developer can not self-evaluate the API surface before applying. Full sourced list under Sources below.
Common alternatives include Globus, Insight Vacations, Collette, Cosmos, CostSaver, Tauck. 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.