Overview
GIATA is a hotel data provider that TripBuilder uses for two core purposes: mapping supplier hotel codes to a universal GIATA property ID (enabling deduplication across suppliers), and enriching hotel properties with geocoordinates and addresses (used for map display, radius/geo search, and timezone resolution).
Tour operators on Maximise and Enterprise plans are required to have their own GIATA credentials. Operators on the Monetise plan are covered by Nezasa's credentials by default, with the option to move to their own credentials after the first 12 months.
Which GIATA contract modules does TripBuilder need?
GIATA's Multicodes product is made up of several modules. Not all of them are used by TripBuilder. The table below shows what is required:
GIATA Multicodes module | Needed? | Why |
Supplier and Tour Operator Codes | Yes — mandatory | This is the core reason TripBuilder uses GIATA. It maps supplier hotel codes to a universal GIATA ID, enabling property clustering and deduplication across suppliers (Hotelbeds, Ratehawk, TBO, Expedia, Sunhotels, and others). |
GeoCodes / Property Addresses | Yes — in practice mandatory | TripBuilder imports lat/long and address per property for map display, radius/geo search, and timezone resolution. The timezone is derived from the coordinates. |
Supplier Code Information, Location | No | TripBuilder does not read location data attached to supplier codes. Only the provider name, code value, and status are imported from each provider block. |
Chain and Group Affiliations | No | TripBuilder has no chain or brand field in its property model. This module is not used. |
Other GIATA products
Beyond Multicodes, GIATA offers several additional products. Here is how they relate to TripBuilder:
GIATA product | What it delivers | Needed? |
Multicodes | GIATA ID, supplier code mapping, geocodes, addresses, city/destination/country, airports, rating. | Yes — see the module table above. |
MHG (Multilingual Hotel Guide) | Hotel descriptions and hotel images, priced per language. | Yes, if you want GIATA hotel content (descriptions and images) displayed under your own licence. A single-language licence (e.g. German only) is the cheapest MHG tier. Note that images are language-independent, so MHG is required for hotel pictures regardless of language scope. |
RTM (Room Type Mapping) | Matching of room types across suppliers. | No — RTM runs on the Nezasa side with a single set of credentials. Tour operators do not need their own RTM contract. |
Facts | Structured hotel amenities. | No — not required for the standard TripBuilder setup. |
Prerequisites
A GIATA contract: You must have an active GIATA Multicodes contract covering at minimum the Supplier and Tour Operator Codes and GeoCodes / Property Addresses modules. If you don't have a contract yet, reach out to GIATA's representative — Berthold Holly ([email protected]) — to get set up.
A Nezasa subscription: GIATA integration is available on eligible Nezasa plans. Contact your Nezasa account manager if you're unsure which plan applies to you.
Setting up your GIATA contract ID
Once your GIATA contract is signed, you will receive a numeric GIATA contract ID. Share it with the Nezasa Operations Team, who will configure it on your TripBuilder instance.
The contract ID has two effects in TripBuilder:
It writes your own GIATA copyright notice into hotel descriptions.
It unlocks GIATA property IDs in the Planner, Booking, and Discovery APIs. Without your own contract ID, GIATA IDs are not returned via the APIs.
Languages (MHG)
If you have an MHG licence, TripBuilder requests hotel content in up to 14 languages: English, German, French, Italian, Dutch, Spanish, Finnish, Portuguese, Swedish, Norwegian, Danish, Polish, Turkish, and Romanian. Languages not covered by your MHG contract will return empty — for example, a German-only licence means hotel descriptions will be blank in all other languages.