---
title: "GIATA MultiCodes: Hotel Mapping and Master Data Profile"
description: "A technical profile of GIATA MultiCodes for hotel identity, supplier-code mapping, deduplication and incremental master-data synchronization."
slug: "giata-multicodes"
translationKey: "platform-giata-multicodes"
locale: "en"
type: "profile"
category: "travel-ecosystem"
tags: ["giata","multicodes","hotel-mapping","master-data","deduplication"]
platform: "GIATA MultiCodes"
domain: "giata.com"
vertical: ["hotel"]
publishedAt: "2026-09-26"
updatedAt: "2026-09-26"
reviewedAt: "2026-09-26"
directory: {"status":"active","reviewedAt":"2026-09-26","platformType":"api","roles":["mapping-content","api"],"ecosystemLayers":["data-content"],"turkeyRelevance":"active-market","audiences":["b2b"],"businessModels":[],"integrationMethods":["api","pull"],"docsUrl":"https://info.giata.com/en/knowledge/what-is-multicodes-mc","company":"GIATA","directSupplierParticipation":"unknown","developerDocsAvailable":"yes","pricingAvailabilityModel":"Non-bookable hotel identity and master data; local cache with incremental updates","bookingOwnership":"none","sources":[{"title":"GIATA — What Is MultiCodes?","url":"https://info.giata.com/en/knowledge/what-is-multicodes-mc"},{"title":"GIATA — MultiCodes API retrieval","url":"https://info.giata.com/en/knowledge/how-do-i-retrieve-multicodes-data"},{"title":"GIATA — MultiCodes API specification","url":"https://info.giata.com/en/knowledge/is-a-specification-for-your-web-service-multicodes-available"}]}
sources:
  - title: "GIATA — What Is MultiCodes?"
    url: "https://info.giata.com/en/knowledge/what-is-multicodes-mc"
  - title: "GIATA — MultiCodes API retrieval"
    url: "https://info.giata.com/en/knowledge/how-do-i-retrieve-multicodes-data"
  - title: "GIATA — MultiCodes API specification"
    url: "https://info.giata.com/en/knowledge/is-a-specification-for-your-web-service-multicodes-available"
---
GIATA MultiCodes is a hotel-mapping and master-data product that links supplier-specific accommodation codes to a shared GIATA-ID. Official documentation positions it as an identity and deduplication layer rather than a booking or availability API.

## Ecosystem role

MultiCodes belongs in the data/content layer of travel distribution. When an OTA, bedbank or metasearch service consumes multiple supplier feeds, the same physical hotel can arrive under different supplier IDs; a canonical mapping layer reduces duplicate listings and identity ambiguity.

## Data model

Official material describes master data such as property names, addresses, coordinates, chain affiliations and supplier codes around the GIATA-ID. Mapping does not create transaction or availability state; it helps downstream search, comparison and booking systems build a cleaner entity graph.

## Synchronization model

GIATA recommends local storage instead of live-query use, with incremental retrieval for changed or moved properties. Daily delta processing, inactive-code handling and preservation of source-provider codes are therefore operationally important.

## Modeling implications

An internal canonical-hotel ID does not have to equal a GIATA-ID. GIATA-ID can be a strong external identity while provenance, supplier-code history, local overrides and human-review state remain separate.

## Turkey context

For systems aggregating Turkish hotel inventory from multiple OTAs, bedbanks or connectivity providers, a mapping layer such as GIATA may be less visible than a retail channel but is important for duplicate prevention and hotel-identity quality.