Booking data

In the process of integrating a travel brand into the Travelpayouts partner platform, you need to set up sending booking data to our system. This is done in order to provide partners with maximum information about orders that are made through their projects.

Depending on the type of tourist facility, the transmitted data must contain a certain set of fields. At the same time, you can transmit more data in additional fields, but the fields listed below must be present.

The data must be transmitted in JSON format.

Flight tickets

The data array with information about sold/booked air tickets must contain:

  • product_type — product type, must be flights
  • departure_country — country of departure in ISO 3166–1 alpha-2 format (US)
  • departure_city — departure city in English
  • departure_datetime — departure date and time in YYYY-mm-dd HH format:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • arrival_country — country of arrival in ISO 3166–1 alpha-2 format (US)
  • arrival_city — city of arrival in English (New York)
  • arrival_datetime — date and time of arrival in YYYY-mm-dd HH format:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • adults — number of adults (over 18 years old)
  • children — number of kids (under 18)
  • passengers — total number of passengers can be specified instead of adults and children
  • any other information about the flight.

Railway tickets

The data array containing information about railway tickets sold/booked must contain:

  • product_type — product type, must be train
  • departure_country — country of departure in ISO 3166–1 alpha-2 format (US)
  • departure_city — departure city in English
  • departure_datetime — departure date and time in YYYY-mm-dd HH format:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • arrival_country — country of arrival in ISO 3166–1 alpha-2 format (US)
  • arrival_city — city of arrival in English (New York)
  • arrival_datetime — date and time of arrival in YYYY-mm-dd HH format:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • adults — number of adults (over 18 years old)
  • children — number of kids (under 18)
  • passengers — total number of passengers can be specified instead of adults and children.

Bus service

The data array with information about bus tickets sold/booked must contain:

  • product_type — product type, must be bus
  • departure_country — country of departure in ISO 3166–1 alpha-2 format (US)
  • departure_city — departure city in English
  • departure_datetime — departure date and time in YYYY-mm-dd HH format:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • arrival_country — country of arrival in ISO 3166–1 alpha-2 format (US)
  • arrival_city — city of arrival in English (New York)
  • arrival_datetime — date and time of arrival in YYYY-mm-dd HH format:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • adults — number of adults (over 18 years old)
  • children — number of kids (under 18)
  • passengers — total number of passengers can be specified instead of adults and children.

Package tours

The data array with information about sold/booked tours should contain:

  • product_type — product type, must be package_tours
  • flight — flight information:
    • departure_country — country of departure in ISO 3166–1 alpha-2 format (US)
    • departure_city — departure city in English
    • departure_datetime — departure date and time in YYYY-mm-dd HH format:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
    • arrival_country — country of arrival in ISO 3166–1 alpha-2 format (US);
    • arrival_city — city of arrival in English (New York)
    • arrival_datetime -date and time of arrival in the format YYYY-mm-dd HH: MM: SS (if there is no HH: MM: SS, you can write 00:00:00)
  • check_in_date — check-in date in YYYY-mm-dd format
  • nights — number of nights of the tour
  • city — city of residence in English
  • name — the name of the hotel in English
  • adults — number of adults (over 18 years old)
  • children — the number of kids (under 18).

Insurance

The data array with information about sold/booked insurance must contain:

  • product_type — product type, must be insurance
  • start_date — start date of the insurance in YYYY-mm-dd format
  • end_date — the date of expiry of the insurance in the YYYY-mm-dd format
  • countries — countries where insurance is valid in the ISO 3166–1 alpha-2 (US) format
  • type — type of insurance (travel, etc.)
  • insurance_company is an insurance company.

Car rental

The data array with information about the sold/booked cars must contain:

  • product_type — product type, must be car_rental
  • departure_country — the country where the car was rented, in the ISO 3166–1 alpha-2 (US) format
  • departure_city — the city where the car was rented, in English
  • departure_datetime — date and time in the format YYYY-mm-dd HH:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • arrival_country — country where the car was returned, in ISO 3166–1 alpha-2 (US) format
  • arrival_city — city where the car was returned, in English (New York)
  • arrival_datetime — date and time of return of the car in the format YYYY-mm-dd HH:MM:SS (if there is no HH:MM:SS, you can write 00:00:00).

Transfers

The data array with information about the sold / booked transfers must contain:

  • product_type — product type, must be transfers
  • departure_country — country of departure in ISO 3166–1 alpha-2 format (US)
  • departure_city — departure city in English
  • departure_datetime — departure date and time in YYYY-mm-dd HH format:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • arrival_country — country of arrival in ISO 3166–1 alpha-2 format (US)
  • arrival_city — city of arrival in English (New York).

Excursions

The data array with information about sold/booked excursions should contain:

  • product_type — product type, should be activities
  • country — excursion country in ISO 3166–1 alpha-2 (US) format
  • city — the city of the excursion in English
  • start_datetime — date and time of the tour in the format YYYY-mm-dd HH:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • info — the name of the excursion.

Sea voyages

The data array with information about sold/booked cruises should contain:

  • product_type — product type, must be cruises
  • departure_country — country of departure in ISO 3166–1 alpha-2 format (US)
  • departure_city — departure city in English
  • departure_datetime — departure date and time in YYYY-mm-dd HH format:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • arrival_country — country of arrival in ISO 3166–1 alpha-2 format (US)
  • arrival_city — city of arrival in English (New York)
  • arrival_datetime — date and time of arrival in YYYY-mm-dd HH format:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • adults — number of adults (over 18 years old)
  • children — number of kids (under 18)
  • passengers — total number of passengers can be specified instead of adults and children.

Accommodation

An array of data with information about sold/booked hotels/apartments should contain:

  • product_type — product type, should be accommodation
  • check_in_date — check-in date in YYYY-mm-dd format
  • check_out_date — check out date in YYYY-mm-dd format
  • nights — number of nights
  • country — country of residence in ISO 3166–1 alpha-2 (US) format
  • city — city of residence in English
  • adults — number of adults (over 18 years old)
  • children — the number of kids (under 18).

Legal advice

The data set with information on legal aid should contain:

  • product_type — product type, should be compensation
  • info — information about the service.

Parking

The data array with information on parking reservations must contain:

  • product_type — product type, must be parking
  • country — country in ISO 3166–1 alpha-2 (US) format
  • city — city in English
  • location — location in the city
  • start_datetime — date and time of the start of parking in the format YYYY-mm-dd HH:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • duration — parking duration.

SIM cards

An array of data with information about SIM cards should contain:

  • product_type — product type, must be sim
  • info — card type, if any.

Carpooling service

An array of data with information about the search for travel companions should contain:

  • product_type — product type, must be carpooling
  • departure_country — country of departure in ISO 3166–1 alpha-2 format (US)
  • departure_city — departure city in English
  • departure_datetime — departure date and time in YYYY-mm-dd HH format:MM:SS (if there is no HH:MM:SS, you can write 00:00:00)
  • arrival_country — country of arrival in ISO 3166–1 alpha-2 format (US)
  • arrival_city — city of arrival in English (New York)
  • passengers — total number of passengers can be specified instead of adults and children.

Restaurants

A data array with information about restaurant reservations should contain:

  • product_type — product type must be food
  • country — country in ISO 3166–1 alpha-2 (US) format
  • city — city in English
  • location — the name of the restaurant
  • start_datetime — the date and time of the restaurant reservation in the format YYYY-mm-dd HH: MM: SS (if there is no HH: MM: SS, you can write 00:00:00).

Bank cards

An array of data with information about bank cards should contain:

  • product_type — product type, must be bank_cards
  • product_name — product name
  • info — information about the card.

Sanatoriums

An array of data with information about sold/booked resorts should contain:

  • product_type — product type, must be sanatoriums
  • check_in_date — check-in date in YYYY-mm-dd format
  • check_out_date — check out date in YYYY-mm-dd format
  • nights — number of nights
  • country — country of residence in ISO 3166–1 alpha-2 (US) format
  • city — city of residence in English
  • name — the name of the sanatorium
  • adults — number of adults (over 18 years old)
  • children — the number of kids (under 18).

Business lounges at airports

An array of data with information about business lounges should contain:

  • product_type — product type, must be airport_lounges
  • product_name — product name
  • start_date — start date of the access in YYYY-mm-dd format
  • end_date — access expiration date in YYYY-mm-dd format
  • passengers — the total number of visitors.