gettour - optionals

New field: optionals

gettour now returns optional excursions associated with the tour.

Fields: brochure, code, name, text

Important: this block is informational only.
Use getoptionals for date-specific optionals and prices.

supplement - iscommissionable

New field: iscommissionable

Values:

• true: commissionable supplement
• false: non-commissionable supplement
• null: not applicable

Commission percentage is still obtained from getcommission.

bookprice / booktour / getreservationservices - generalconditions

New field: generalconditions

Includes:

• title
• summary
• PDF URL

Available in Spanish, English and Portuguese.

bookprice / booktour / getreservationservices - departurewarning

New field: departurewarning

Returned when booking less than 30 days before departure.

If not applicable:

{
  "departurewarning": ""
}

Compatibility

These changes are backward compatible and do not require mandatory integration changes.

gettour - optimized response

The gettour response has been optimized to reduce duplicated information.

Some repeated data inside hotels and pickups has been removed because it is already available in the main tour response.

This reduces the response size while keeping the functional information available.

getreservationservices - lite response by default

The getreservationservices response is now returned in lite mode by default, reducing the amount of data included in each reservation service.

If the full response is required, send:

{
  "lite": false
}

Example:

{
  "logindata": {
    "useremail": "useremail",
    "userpass": "userpass",
    "integrator_token": "integrator_token"
  },
  "requestdata": {
    "language": "1",
    "reservationcode": 99999,
    "lite": false
  }
}

The getreservationservices response now includes an itinerary block at the end of the response.

This block returns the itinerary with the real dates of the reservation.

Example:

{
  "itinerary": [
    {
      "code": "1",
      "date": "2025-12-19",
      "title": "Día 1º (Viernes) AMERICA-MADRID",
      "text": "Salida en vuelo intercontinental hacia Madrid. Noche a bordo."
    },
    {
      "code": "2",
      "date": "2025-12-20",
      "title": "Día 2º (Sábado) MADRID",
      "text": "Llegada al aeropuerto internacional de Madrid-Barajas. Asistencia y traslado al hotel. Alojamiento y resto del día libre"
    }
  ]
}

gettour - citiesroute

New field: citiesroute

gettour now includes the citiesroute array.

This field returns the cities included in the tour route, including both overnight cities and transit / visit cities.

Example:

 json
{
  "citiesroute": [
    {
      "code": 2638,
      "name": "ESTAMBUL"
    },
    {
      "code": 28351,
      "name": "CAPADOCIA"
    },
    {
      "code": 94660,
      "name": "ISTANBUL"
    },
    {
      "code": 94228,
      "name": "IZMIR"
    },
    {
      "code": 66254,
      "name": "KUSADASI"
    },
    {
      "code": 66255,
      "name": "PAMUKKALE"
    },
    {
      "code": 28346,
      "name": "ANKARA"
    },
    {
      "code": 3231,
      "name": "BURSA"
    },
    {
      "code": 95045,
      "name": "SELÇUK"
    }
  ]
}

This field has been created mainly for external circuits, where it may be necessary to know all cities included in the route, not only the cities where the passenger stays overnight.

The information will be incorporated progressively, so some tours may return an empty citiesroute array or may not include all route cities initially.

This field is informational and should not be used to determine overnight stays, hotels or itinerary dates.

Compatibility

This change is backward compatible and does not require mandatory integration changes.