ETG API V3
API usage advices

API usage advices

Usage of static data

You can access the static data via the corresponding API calls:

  • Retrieve hotel incremental dump (B2B, Affiliate):
    • Provides data on the ETG hotels whose content has changed in the previous day.
    • Each archive is meant for a single language.
  • Retrieve hotel dump (B2B, Affiliate):
    • Provides data on all hotels available in the ETG API.
    • Each archive is meant for a single language.
  • Retrieve regions’ dump (B2B, Affiliate):
    • Provides data on the hotels in all regions available in the ETG API.
    • Each archive is meant for a single language.

Update time for the static data

  • Retrieve hotel incremental dump (B2B, Affiliate). Update daily.

    ℹ️
    If you use the incremental dump, there’s no need to download the entire dump.

  • Retrieve hotel dump (B2B, Affiliate). Update weekly.

  • Retrieve regions’ dump (B2B, Affiliate). Update weekly.

Static data matching

To match data from the search request with static room data (such as room images and amenities), use the values found in the rg_ext response field within a hotel.

Mapping logic and mapping updates

Along with hotel static data, update the hotel mapping on a daily or weekly basis.

Search steps

Use the calls made by the SERP mechanism:

  • In the first search step, show one or two of the cheapest rates for each hotel.
  • In the second search step, show all the rates for one specific hotel.

Not advised

Pay attention to this non-advisable information because you:

  • May miss a significant number of available rates.
  • Might experience a higher failure rate during the valuation step.

We don’t advise using the rates matching workflow due to these reasons:

  • Booking restrictions. Some suppliers don’t allow you to make a booking directly from the first search step.
  • Incomplete data. Some suppliers don’t provide all the necessary information at the first search step. For example, cancellation policies might be missing.
  • Limited rate availability. Some suppliers only provide one of the cheapest rates at the first search step. Other available rates might be missed.
  • Search step time. The first search step may be slower. The rates might be missed if you have a short search timeout.
  • Cache lifetime. The first search step has a longer cache lifetime. The rates might be outdated.

If you still wish to match the rates retrieved within 3-step search, use the match_hash field from the search response.

Residency

The rates in the first search response are provided according to the nationality of the first guest provided in the search request. Nationality should be the same for each guest in every search request. Provide the real guests’ nationality in the residency field.

Meal types

The ETG provides a wide range of meal types. To get all available meal types and their definitions, use the meal field from the Retrieve hotel static data call.

Final price and commission

The ETG API provides both gross and net prices in the currencies:

  • The contracted — amount_charge.
  • The requested — amount_show.

To retrieve commission details, use the amount_commission field.

Mandatory information

It is mandatory to display the “Important information” section for hotels. To fill the section with hotel rules and chargeable services’ information, use the fields:

  • Static data step:
    • metapolicy_struct — additional accommodation conditions.
    • metapolicy_extra_info — additional hotel information.
  • Search step:
    • tax_data — taxes and fees.
    • room_name — full room type.

Cache

If you don’t expect the rates to be available when creating the booking, you may cache them.

The longer a rate is stored in the cache, the higher the likelihood that it will no longer be available later.

Timeout

To apply the incoming timeout to the search response, use the timeout request field.

ℹ️
If you work with dynamic search timeouts, ensure you implement the timeout field.

Booking steps

  • To receive the final status of the booking, use one of the calls:
  • If you use the Check booking process (B2B, Affiliate) call, check the status of the booking every 5 seconds until the final status is obtained.
  • If you have any limitations for this step, contact the API support team.

Cut-off logic

The ETG API doesn’t support incoming booking timeouts. You can manually apply the booking cut-off logic to the related API key. To discuss a change, contact the API support team.

5xx, unknown, and timeout errors

Errors with 5xx HTTP status, unknown errors, or timeouts during the booking process don’t necessarily indicate a booking failure.

If you encounter these errors, follow the error descriptions of the corresponding call: