What you can build

tourpingo is a marketplace and booking engine for travel. Its sellers are local guides and tour operators in many destinations: Vacation Packages Oman in Muscat, Dubai Fly Tours in Dubai, Vacations of Africa in Tanzania, and more. They sell private, shared and group tours, day trips and multi-day trips.

tourpingo keeps each seller’s trips, prices, calendar and bookings. You build on top of them with two APIs.

A seller’s own website

The public API (/v1/public/*) is everything a booking website needs:

• the seller’s trips, with photos, itineraries and a “from” price;
• search, filters, cities, places and categories;
• a trip’s calendar, with the places left on each start;
• a quote for the travellers chosen, then a hold, then checkout;
• a page where the traveller sees, pays, fills in or cancels a booking;
• enquiries, and the site’s own pages, menus and old addresses.

It uses the site’s website key, which ties every request to one seller’s site. The seller collects the money for bookings made there. tourpingo’s own marketplace runs on this same API, with a key that sells every seller’s trips.

Start with the quick start, then the website guides.

A link from a seller’s own systems

The seller API (/v1/*) is what tourpingo’s portal uses: trips, options, prices, availability and bookings, for one seller. With a secret key a seller’s own system can, for example, import its trips or copy its bookings into its accounts. See which key to use.

Not there yet

These are planned, and the guides say so where they matter:

• Webhooks, so your site hears of a new or cancelled booking without asking: issue #522.
• A booking flow to embed with a script tag, for a site that isn’t built on the API: issue #533.
• A TypeScript client generated from the spec: issue #486.
• Card payments: today a booking is paid by bank transfer, a payment link or on the day.
• Sites hosted by tourpingo on a seller’s own domain, for sellers with no developers.