ETG API V3
Integration guide

Integration guide

To integrate the ETG API, use the suggested workflow:

  1. Download the hotels’ static data.
  2. Search a hotel.
  3. Make a booking.
  4. Make the post-booking routine.
  5. Proceed with the certification and provide access to your test and production website where the ETG API is implemented.

Download hotels’ static data

  1. Required. Get a dump (B2B, Affiliate).
  2. Optional. Search for static hotel data (B2B, Affiliate). Is used only in case when an available hotel isn’t included in the downloaded hotel data dump. It can happen to new hotels in the ETG inventory.

Search hotel

  1. Required. Search for an available hotel with geo, regions, or hotels. Is used for the initial dynamic search of hotels with available accommodations that match the given search.

    ℹ️

    The recommendations:

    • Don’t allow users to choose rates through this call, as it doesn’t guarantee a complete match with results from the Hotelpage (B2B, Affiliate) call.
    • During the call, display one or two of the most affordable rates for each hotel.

  2. Required. Make a pre-booking by one of the ways:

General pre-booking

ℹ️
Is required if you intend to use the Hotelpage call as a part of your flow.

  1. Required. Get the hotel rates list (B2B, Affiliate). Use it only for the hotel the end-user wants to know about.

    ℹ️

    The recommendations:

    • Don’t use the call for every hotel found via the region_id field or its IDs.
    • Use the call only when the user selects it.
    • During the call, display all rates for a specific hotel.
    • The storage time for retrieved rates is 1 hour.
    ⚠️
    Don’t use this call to initiate the search automatically for all hotels returned by a region search.

  2. Required. Make a pre-booking (B2B, Affiliate). Is used to getting the availability of the requested rate.

    ℹ️

    The recommendations:

    • If the original rate isn’t available, the call will try to find the same or similar rate.
    • The price_increase_percent feature:
      • Provides the possibility to find the best alternative for the chosen rate within the selected price increase range.
      • When implemented, the user should be notified about the price change before the booking step. Otherwise, it isn’t suggested to implement.

Simplified pre-booking

ℹ️
Is required if you don’t intend to use the Hotelpage call as a part of your flow.
  1. Required. Make a pre-booking (B2B, Affiliate). Is used to getting the availability of the requested rate.

Make booking

  1. Required. Start creating a booking (B2B, Affiliate).
  2. Required. Complete the booking creation (B2B, Affiliate).
  3. One of them is required. To get the booking status, use one of the calls:

Make post-booking routine

  1. Optional. Get information on the completed booking (B2B, Affiliate).

    ℹ️

    The recommendations:

    • Use the call 8 seconds after the booking is completed.

  2. Optional. Cancel the completed booking (B2B, Affiliate).

GlossaryRequests