Business Platform
TravelShop

Riferimento API

API di TravelShop Booking

Cerchi tra oltre 10.000 tour, ottenga prezzi e disponibilità in tempo reale e crei prenotazioni dalla sua piattaforma. Questo riferimento è pubblico: lo legga prima di candidarsi.

Per iniziare

L’API è una semplice API REST su HTTPS che restituisce JSON, autenticata con un’unica chiave API che genera in autonomia dopo l’approvazione dell’accesso. Gli esempi seguenti usano {BASE_URL} come segnaposto: il suo URL di base è indicato accanto alla chiave nella dashboard sviluppatori.

  1. 1

    Candidatura

    Ci parli della sua piattaforma. Esaminiamo manualmente ogni richiesta, di solito entro 1–2 giorni lavorativi.

  2. 2

    Generi la chiave

    Dopo l’approvazione, crei la sua chiave API nella dashboard sviluppatori e registri gli indirizzi IP dei server che chiameranno l’API. La chiave viene mostrata una sola volta.

  3. 3

    Chiami l’API

    Invii la chiave nell’header X-API-Key a ogni richiesta. Non serve nient’altro.

Autenticazione

Invii la sua chiave nell’header X-API-Key a ogni richiesta. Nessun flusso OAuth, nessuno scambio di token e nessuna scadenza: la chiave resta valida finché non la rigenera o la revoca.

curl
curl -X GET '{BASE_URL}/b2b/api/apiv2/b2c/tours/search?term=cappadocia&page_size=5' \
  -H 'X-API-Key: YOUR_API_KEY' \
  -H 'Accept: application/json'
node
const res = await fetch(
  '{BASE_URL}/b2b/api/apiv2/b2c/tours/search',
  {
    method: 'POST',
    headers: {
      'X-API-Key': process.env.TSB_API_KEY,
      'Content-Type': 'application/json',
      Accept: 'application/json',
    },
    body: JSON.stringify({ term: 'cappadocia', page_size: 5 }),
  },
)

const data = await res.json()
Chiami l’API dal suo server, mai dal codice del browser: una chiave inviata al browser è una chiave pubblica. Conserviamo solo una copia hash della sua chiave, quindi viene mostrata una sola volta, al momento della creazione. L’ha persa? Ne generi una nuova: quella vecchia smette subito di funzionare.

Elenco IP autorizzati

Gli endpoint partner accettano richieste solo dagli indirizzi IP dei server che ha registrato. Dopo l’approvazione dell’accesso, aggiunga nella dashboard sviluppatori gli indirizzi IP pubblici che i suoi server usano per le richieste in uscita — fino a 3 indirizzi per impostazione predefinita.

  • Registri singoli indirizzi IPv4 o IPv6. Intervalli, indirizzi privati o riservati e indirizzi di proprietà di Cloudflare vengono rifiutati.
  • Usi l’indirizzo da cui il suo server invia le richieste, non l’IP del suo sito web. Se il sito è dietro Cloudflare, quell’indirizzo appartiene a Cloudflare e non può essere registrato.
  • Se il suo server dispone di IPv6, le richieste potrebbero uscire tramite IPv6. Registri anche quell’indirizzo oppure forzi il suo client HTTP a usare IPv4. Esegua i comandi seguenti direttamente sul server per vedere entrambi gli indirizzi.
  • Le modifiche diventano effettive entro circa un minuto.
curl
curl -4 https://api.ipify.org
curl -6 https://api64.ipify.org

Quando una richiesta viene bloccata

Le richieste da un IP non registrato vengono bloccate prima di raggiungere l’API: invece di un errore JSON riceve un HTTP 403 con una pagina di verifica HTML intitolata "Just a moment...". Finché non registra un IP, la chiave in sé non è limitata per IP, ma le richieste dai suoi server riceveranno questa pagina. Se la vede, verifichi quale IP usa effettivamente il suo server e registri quell’indirizzo.

Non appena registra almeno un IP, la sua chiave viene accettata solo da quegli indirizzi. Una richiesta con la sua chiave che raggiunge l’API da qualsiasi altro IP viene rifiutata con 403 e il codice ip_not_allowed; il corpo della risposta riporta l’IP rilevato. Una chiave trafugata è inutilizzabile al di fuori dei suoi server.

Risposta 403
{
  "message": "This API key is not allowed from your IP address. Register it under Allowed server IPs in your developer dashboard.",
  "code": "ip_not_allowed",
  "ip": "203.0.113.10"
}

Limiti di frequenza e quote

Si applicano due limiti indipendenti, entrambi calcolati per singolo partner e mai condivisi con altri.

240 richieste al minuto

Un limite sui picchi. Ogni risposta include X-RateLimit-Limit e X-RateLimit-Remaining, così può regolare il ritmo delle chiamate.

20000 richieste al giorno

La quota giornaliera predefinita al momento dell’approvazione. Si azzera a mezzanotte UTC e la aumentiamo su richiesta: ci indichi il volume previsto e ci adegueremo.

Il superamento di uno dei due limiti restituisce 429. L’utilizzo attuale, suddiviso per endpoint, è visibile nella sua dashboard sviluppatori.

Regole sui contenuti

I nuovi tour vengono trattenuti per 30 giorni. Un tour aggiunto al nostro catalogo non compare nei risultati di ricerca partner, nel dettaglio del tour né nelle risposte su prezzi e disponibilità finché non sono trascorsi 30 giorni. Le richieste su un singolo tour rispondono 404 con il codice tour_embargoed e la data in cui il tour sarà disponibile. Così il tour ha il tempo di essere indicizzato prima sul nostro sito e i motori di ricerca vedono la fonte originale. Tutti i tour più vecchi sono pienamente disponibili. Se è anche un nostro fornitore e il suo account è collegato alla sua azienda fornitrice, i suoi tour sono esenti: sono disponibili tramite API immediatamente, senza alcun periodo di attesa.

Prezzi, date e contenuti vengono riverificati ogni giorno. Può memorizzare le risposte in cache, ma aggiorni prezzi e disponibilità almeno una volta al giorno — e verifichi sempre di nuovo la disponibilità subito prima di creare una prenotazione.

Catalogue synchronization

Import complete public tour content and current retail departure schedules through two paginated change feeds.

With pricing=default, use pricing.reference.amount for your reference price. It follows the supplier detail page’s initial traveller count and first available month, with regular retail pricing preferred when offered, otherwise private. The amount is already discounted in EUR. Minimum 0 or 1 selects three travellers capped by the maximum; another minimum selects that minimum. A null reference means no displayable initial price. Do not substitute a minimum over raw rates.

The schedule feed additionally returns pricing.options: equal EUR prices grouped by explicit dates for the default traveller count. Promotions are already applied. In this mode, crossing an hour since modified-since refreshes authorized schedules even without rate edits. A cursor is bound to its pricing mode. On upgrade, restart product pagination from the last saved modified-since to preserve removal markers, and restart schedules with a full scan.

For the first scan, omit modified-since. Follow nextCursor until it is null, sending each cursor without modified-since. Save syncStartedAt from the first page; send it as modified-since on the next run. Each cursor belongs to one partner account and one feed. Apply records by tourId and allow duplicate updates at time boundaries.

Initial scans contain only active, non-deleted, non-custom tours. Incremental product scans return a minimal INACTIVE record when a previously public tour is disabled, made custom or soft-deleted; remove or hide that tour and its saved schedule locally. No disabled tour content or prices are returned. The schedule feed stays active-only. The content embargo applies, except to your own supplier tours when your account is linked. Use syncStartedAt, not an item’s modifiedAt, as the next checkpoint.

Departure dates can pass without a database modification. Remove past dates locally; each incremental schedule update replaces the complete saved schedule for that tour.

GET/b2b/api/products/modified-since

New and modified products

An ACTIVE item contains tourId, slug, modifiedAt, status and product with full public tour content. An INACTIVE item contains only tourId, slug, modifiedAt and status; remove or hide the saved tour. If republished, it arrives again as ACTIVE. Net prices and private company fields are excluded.

ParametroTipoDescrizione
modified-sinceISO 8601Timestamp with a timezone offset, for example 2026-10-20T09:00:00Z. Omit for an initial full scan.
countintegerPage size from 1 to 500; defaults to 100.
cursorstringOpaque nextCursor from the previous page. Send it without modified-since.
pricingdefaultOpt in to the public detail page’s default B2C reference quote. Send pricing=default on every cursor page too. Adds pricingPolicy and per-tour pricing.
activeCurrencyEURWith pricing=default, EUR is the only accepted currency and is the default. The legacy raw rates keep their native currencies.
Default reference price in EUR
curl -G '{BASE_URL}/b2b/api/products/modified-since' -H 'X-API-Key: YOUR_API_KEY' --data-urlencode 'pricing=default' --data-urlencode 'activeCurrency=EUR' --data-urlencode 'count=100'
Initial request
curl -G '{BASE_URL}/b2b/api/products/modified-since' -H 'X-API-Key: YOUR_API_KEY' --data-urlencode 'count=100'
Next page
curl -G '{BASE_URL}/b2b/api/products/modified-since' -H 'X-API-Key: YOUR_API_KEY' --data-urlencode 'cursor=NEXT_CURSOR'
Response (product abbreviated)
{
  "products": [
    {
      "tourId": 123,
      "slug": "example-tour",
      "modifiedAt": "2026-10-20T08:00:00+00:00",
      "status": "ACTIVE",
      "product": {
        "id": 123,
        "slug": "example-tour",
        "name": "Example tour",
        "itineraries": []
      }
    }
  ],
  "nextCursor": null,
  "syncStartedAt": "2026-10-20T09:00:00+00:00"
}
Incremental removal marker
{
  "products": [
    {
      "tourId": 123,
      "slug": "example-tour",
      "modifiedAt": "2026-10-20T08:15:00+00:00",
      "status": "INACTIVE"
    }
  ],
  "nextCursor": null,
  "syncStartedAt": "2026-10-20T09:00:00+00:00"
}

INACTIVE records contain no product details or prices. Only active tours appear in an initial scan. A complete incremental scan and saved checkpoint replace periodic full-catalogue comparison for later soft deletions. If active content is temporarily unavailable, retry the 503 page without advancing its cursor.

GET/b2b/api/availability/schedules/modified-since

Modified availability schedules

Each availabilitySchedules[] item contains tourId, slug, modifiedAt and rates: the complete current set of retail rates for that tour, not just the changed rate. Each rate includes its dates from today onward.

ParametroTipoDescrizione
modified-sinceISO 8601Timestamp with a timezone offset. Omit for an initial full scan.
countintegerPage size from 1 to 500; defaults to 100.
cursorstringOpaque nextCursor from the previous page. Send it without modified-since.
pricingdefaultOpt in to the public detail page’s default B2C reference quote. Send pricing=default on every cursor page too. Adds pricingPolicy and per-tour pricing.
activeCurrencyEURWith pricing=default, EUR is the only accepted currency and is the default. The legacy raw rates keep their native currencies.
Default reference price in EUR
curl -G '{BASE_URL}/b2b/api/availability/schedules/modified-since' -H 'X-API-Key: YOUR_API_KEY' --data-urlencode 'pricing=default' --data-urlencode 'activeCurrency=EUR' --data-urlencode 'count=100'
Incremental request
curl -G '{BASE_URL}/b2b/api/availability/schedules/modified-since' -H 'X-API-Key: YOUR_API_KEY' --data-urlencode 'modified-since=2026-10-20T09:00:00Z'
Response
{
  "availabilitySchedules": [
    {
      "tourId": 123,
      "slug": "example-tour",
      "modifiedAt": "2026-10-20T08:00:00+00:00",
      "rates": [
        {
          "rateId": 456,
          "startsAt": "2026-11-01",
          "endsAt": "2026-11-30",
          "minPax": 1,
          "maxPax": 20,
          "currency": "EUR",
          "departureTypeId": "scheduled",
          "description": {
            "en": "Standard departure"
          },
          "prices": {
            "regular": {
              "dbl": 200
            }
          },
          "dates": [
            "2026-11-05"
          ]
        }
      ]
    }
  ],
  "nextCursor": null,
  "syncStartedAt": "2026-10-20T09:00:00+00:00"
}

When the last rate is deleted, the tour is returned with rates: [] so you can clear its saved schedule. A rate can have a valid period but dates: []. Prices are retail only; supplier net prices and markup are never returned. Successful pages use Cache-Control: private, no-store.

Pricing & availability

Live departure availability and B2C retail prices. Partner API keys do not provide access to supplier net prices.

GET/b2b/api/apiv2/b2c/availability/{slug}

Availability & price for a tour

Departure availability and retail pricing for one tour.

ParametroTipoDescrizione
roomTypestringsng, dbl or trp. Defaults to dbl.
dateYYYY-MM-DDA single departure date.
startDateYYYY-MM-DDStart of a date range.
endDateYYYY-MM-DDEnd of a date range.
paxintegerNumber of travellers.
service_typestringService level. Defaults to regular.
roomsarrayRoom breakdown, as [{ id, pax, count }].
include_pricesyes | noInclude the price breakdown.
include_roomsyes | noInclude room options.

An unavailable, deleted, or embargoed tour returns 404.

POST/b2b/api/apiv2/b2c/prices/{type}

Batch prices

One retail price per tour for a list of ids — what listing and category pages need.

ParametroTipoDescrizione
idsobbligatoriointeger[]Tour ids to price.
roomTypestringsng, dbl or trp. Defaults to dbl.
startDateYYYY-MM-DDDefaults to today.
endDateYYYY-MM-DDOptional range end.

Unavailable, deleted, and embargoed tours are left out of the response.

GET/b2b/api/apiv2/b2c/pricemonths/{type}/{id}

Available months

Available month dates for a tour, for building a departure calendar. This endpoint does not return prices.

An unavailable, deleted, or embargoed tour returns 404.

Destinations & taxonomy

The reference data behind filters, menus and search boxes.

GET/b2b/api/apiv1/b2c/countries/list

Countries

All countries with their id, name, slug and phone code.

GET/b2b/api/apiv1/b2c/quicksearch/locations

Location search

Search destinations by name — cities, regions and countries.

ParametroTipoDescrizione
qstringSearch term.
idsstringComma-separated ids, to resolve known locations instead of searching.
limitintegerMax results, 1–50. Defaults to 20.
GET/b2b/api/apiv1/location-parents/{id}

Location ancestors

The parent chain of a location (city → region → country), for breadcrumbs.

GET/b2b/api/apiv1/b2c/quicksearch/tour-categories

Tour categories

Category pages matching a term, with their titles and URLs.

ParametroTipoDescrizione
termstringSearch term.
GET/b2b/api/apiv1/b2c/quicksearch/activities

Activities

Activity list (hiking, diving, …) with id, name and slug — the values the activities filter accepts.

ParametroTipoDescrizione
termstringSearch term.
GET/b2b/api/apiv1/b2c/tours/available-destinations

Available destinations

Destinations that currently have bookable tours.

Enquiries & bookings

Create demand on our side from your platform. Everything you create here is attributed to your partner account and appears in your dashboard.

POST/b2b/api/apiv1/bookings/new-enquiry

Create an enquiry

A traveller question about a tour. Creates an enquiry record and notifies the operator.

ParametroTipoDescrizione
tour_idobbligatoriointegerThe tour being asked about.
contact_nameobbligatoriostringThe traveller's name.
contact_emailobbligatoriostringThe traveller's email.
messageobbligatoriostringThe question, up to 5000 characters.
phone_codeintegerLocation id of the phone country code.
contact_phonestringPhone number without the country code.
buyer_currencyUSD | EURCurrency to quote in. Defaults to EUR.

No captcha is required on API-key requests — your key, quota and rate limit are the gate.

POST/b2b/api/apiv1/bookings/new-booking

Create a booking

A booking checkout with travellers and rooms, priced from B2C retail availability. Returns the reference_id and token used for payment.

ParametroTipoDescrizione
tour_idobbligatoriointegerThe tour being booked.
paxobbligatoriointegerNumber of travellers.
dateobbligatorioYYYY-MM-DDDeparture date, today or later.
service_typeobbligatoriostringService level, as returned by availability.
buyer_currencyobbligatoriostringCurrency the traveller pays in. The seller currency is taken from the tour’s own price record.
roomsarrayRequired for tours with accommodation: [{ id: "dbl", pax, count }].
customersobbligatorioarrayTravellers. The first is the lead and needs title, first_name, last_name, email, phone_code and phone.
GET/b2b/api/apiv1/bookings/{referenceId}

Booking detail

Read one booking. Pass the booking token as ?token= — the token scopes access to that single booking.

ParametroTipoDescrizione
tokenobbligatoriostringThe token returned when the booking was created.
POST/b2b/api/apiv1/bookings/{referenceId}/payment-request

Open a payment request

Start a collection against a booking, for a payment page hosted on your own front end. Call it from your server; the amount is calculated from the booking — the client cannot set it. The response carries the payment request’s id, reference_id and token, which your payment page needs for the next step (Take the card payment).

ParametroTipoDescrizione
tokenobbligatoriostringThe booking token.
payment_modeltotal | depositCollect the full remaining amount or just the deposit.

Do not send card details here. Card data goes from the traveller’s browser straight to us in the next step, so it never passes through your servers.

POST/payments/pay

Take the card payment

Submit this from the traveller’s browser as a plain HTML form post (not from your server). We pass the card to the bank and the traveller continues on the bank’s 3D Secure page. When the bank is done, the traveller lands on your return_url; read the outcome with Payment request status.

ParametroTipoDescrizione
referenceobbligatoriostringreference_id of the payment request.
tokenobbligatoriostringtoken of the payment request (not the booking token).
return_urlobbligatoriostringWhere the traveller lands after the bank. Must be on the website registered for your partner account, or one of its subdomains.
card_nameobbligatoriostringName on the card.
card_numberobbligatoriostringCard number, digits only.
exp_monthobbligatoriointegerExpiry month, 1–12.
exp_yearobbligatoriointegerExpiry year, two digits.
cvcobbligatoriostringSecurity code.

No X-API-Key on this call — it comes from the traveller’s browser; the payment request’s token is what authorises it. A wrong token, a return_url outside your website, or a closed or cancelled booking is refused.

GET/b2b/api/apiv1/bookings/{referenceId}/payment-request/{id}

Payment request status

Poll the state of a payment request. Requires the same token.

ParametroTipoDescrizione
tokenobbligatoriostringThe booking token.
POST/b2b/api/apiv1/bookings/abandoned-cart

Report an abandoned cart

Tell us a traveller started but did not finish a booking, so our team can follow up. Creates no booking record.

ParametroTipoDescrizione
sourceobbligatoriotsb | tstWhich storefront the cart came from.
tourobbligatoriostringTour slug.
namestringThe traveller's name.
emailstringThe traveller's email.
phone_codeintegerLocation id of the phone country code.
phonestringPhone number.
dateYYYY-MM-DDIntended departure date.
paxintegerNumber of travellers.

Deprecated response fields

Since 3 November 2026, tour search, tour detail and the product feed return the fields below as null. The keys stay in the response until 1 May 2027 so existing integrations keep parsing; after that date they are removed. Do not build on them.

Tour fields: guides, transfers, additional_service_location, is_bokun_completed, free_cancelation, all_inclusive, type, vat, deleted_at, b2c, bokun_id, sales, meta_title, meta_description, content_score and defaults.content_score.

Reviews: reviews is null. The rating and review_count summary is still returned.

name_en keeps its value until 1 May 2027 and is removed after that. Use name instead.

Price fields: the trp_, chd_ and inf_ minimum prices (min_reg_price, min_prv_price and their _pax variants), sng_/dbl_/unit_/adl_min_reg_price_pax and min_prv_price_pax. Keep using price and the sng_/dbl_/unit_/adl_ min_reg_price, min_prv_price and min_prv_price_pax fields; for exact prices and availability, call the pricing endpoints.

In rates[].dates[], id, rate_id and tour_id are null; date is unchanged.

Errori

Gli errori usano i codici di stato HTTP standard, con un corpo JSON che contiene un message e — in caso di errori di validazione — un oggetto errors con chiavi corrispondenti ai nomi dei campi.

CodiceSignificatoCosa fare
200OKThe request succeeded.
401UnauthorizedThe X-API-Key header is missing, or the key is not recognised. Check that you are sending the key you generated, not the one it replaced.
403ForbiddenYour API access is suspended or not yet approved. Contact us if you believe this is a mistake.
403IP not allowedThe body carries code ip_not_allowed and the ip we saw. Your key is bound to the server IPs you registered and this request came from another address. Register that address in your developer dashboard, or send the request from a registered server.
403Challenge pageAn HTML page titled "Just a moment..." instead of JSON. The request came from an IP that is not on your allowlist and was stopped before it reached the API. Register your server’s outgoing IP in your developer dashboard; changes take effect within about a minute.
404Not foundThe tour, booking or location is unavailable, deleted, embargoed or unknown; for token-scoped endpoints, the token may not match.
422UnprocessableValidation failed. The body contains a message; field validation may also include an errors object. For change feeds, check the timestamp, count and cursor, and never send cursor with modified-since.
429Too many requestsYou exceeded either the per-minute rate limit or your daily quota. Check the X-RateLimit-Remaining header and back off.
503Temporarily unavailableThe product change feed could not read complete tour content. Wait for Retry-After, then retry the same page without saving or advancing its cursor.
500Server errorSomething failed on our side. Retry with backoff; if it persists, contact us with the time of the request.
Risposta 422
{
  "message": "The given data was invalid.",
  "errors": {
    "tour_id": ["The selected tour id is invalid."],
    "customers.0.email": ["The customers.0.email must be a valid email address."]
  }
}

Versionamento

Alcuni endpoint mantengono il percorso storico /b2b/api/apiv1/… o /b2b/api/apiv2/…. Gli endpoint partner nativi, inclusi i feed delle modifiche al catalogo, si trovano direttamente sotto /b2b/api/…. Sono tutti attivi e mantenuti.

All’interno di una versione apportiamo solo modifiche additive: nuovi campi e nuovi endpoint. Non rinominiamo né rimuoviamo campi su cui fa già affidamento. Qualsiasi modifica che possa compromettere un’integrazione viene rilasciata con un nuovo percorso di versione, e avvisiamo via e-mail ogni partner attivo prima di dismettere una versione.

Vuole iniziare a sviluppare?

Richieda l’accesso e generi la sua chiave. Ha dubbi su quale integrazione sia più adatta? Il nostro team sarà felice di aiutarla.