TourCMS API Integration Services

Overview

What the TourCMS API actually gives you.

TourCMS provides booking management and a marketplace connecting operators with agents. It has been around a long time, which means two things: it is well established in parts of the industry, and its API predates most of the conventions a developer now expects.

Integrations are typically either an operator connecting their own systems, or an agent pulling operator product to sell. Both are very doable. Both also benefit from someone who has met the system's particular habits before, especially around how its channel and marketplace levels differ.

Capabilities

The parts you will actually use.

Tour search — finding product by keyword or criteria, with the distinction between your own channel and the wider marketplace mattering more than you would expect.
Tour detail — the schedule, start-time behaviour, and pricing for a given tour.
Availability checks — bookable departures for a date, and what is needed to book them.
Bookings — creation, amendment, and cancellation through the booking flow.
Customer data — the booking and customer records behind reporting and support.
Distribution — operator product made available to agents, or agent systems pulling operator product.

Scope

Where these projects actually get hard.

Reading the documentation is the easy half. These are the areas that decide whether an integration takes weeks or months — and the ones we scope carefully before quoting.

Channel level versus marketplace level. The same request does not return the same thing at both levels, and some calls simply will not work for product that is not on your own channel. This accounts for most early confusion.
An older API style. Request signing and payload conventions are not what a modern REST API would do. It works perfectly well; it just needs to be approached on its own terms rather than assumed.
Start-time semantics vary. Products can be single-departure, multi-departure, or open-hours, and they need handling as genuinely different cases rather than one with exceptions.
Cross-account access fails confusingly. Requests for product you do not have rights to do not always fail in an obvious way, which can send you debugging the wrong thing entirely.
Legacy data has history. Long-running accounts accumulate inconsistencies, and a migration or reporting project meets all of them at once.
Integration or migration. Operators who come to us about TourCMS sometimes find the more useful conversation is whether the platform still fits where the business is going.

Integrate or migrate

Often the real question.

TourCMS is both a reservation system and a distribution channel, so an integration is usually about one of two things: getting product out to more places, or getting bookings and data back into the systems you actually run the business on.

We also do migrations. Where a system is being retired, the work is to move the data and the integrations without losing booking history or breaking the channels that are currently selling — which has to be sequenced rather than switched over and hoped for.

What we build

Work we take on.

Operator integrations — TourCMS connected to your website, operations, or accounting systems.
Agent integrations — operator product searched and booked from your own agency platform.
Platform bridges — TourCMS alongside or into another reservation system, kept consistent during transition.
Migrations — off TourCMS onto a current platform, with booking history and live channels preserved.
Reporting — booking and customer data extracted into something you can actually analyse.
Hosted & monitored — integrations run on managed infrastructure with health checks.

FAQ

Common questions

Is the TourCMS API still a reasonable thing to build on?

Yes. It is an older style of API but a stable one, and plenty of real businesses depend on it. The honest caveat is that if you are choosing a platform today rather than integrating one you already run, that is a different conversation and we are happy to have it.

Why do some API calls return nothing for tours I can see?

Most often because the request is being made at the wrong level — your own channel versus the wider marketplace — or against product your credentials do not have rights to. It is rarely a signing problem, though it is usually mistaken for one.

Can you move us off TourCMS onto something newer?

Yes, and we would scope it as a migration rather than an integration: booking history, live channels, and the sequence that avoids a gap in sales. The order of operations is what makes these safe.

Can agents book our tours through their own systems?

Yes, that is one of the platform's purposes. The work is in making sure availability and pricing presented to the agent match what you can actually honour.

Can you extract our booking data for reporting?

Yes. Getting booking and customer history into a warehouse or spreadsheet you control is a common first project, and often the one that pays for itself fastest.

More integrations

Other platforms we connect.

We are usually working in several of these at once, which is how we know where each one bites. See all integrations for the full list.

Integrating TourCMS, or moving off it?

Get in touch

TourCMS API Integration