Map hotel property IDs across systems using GIATA multi-codes
domain: hotel-content · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register with GIATA (or a GIATA-licensed data provider) to obtain access to the multi-codes database, which maps proprietary hotel IDs across GDS systems, OTAs, and bed banks to a canonical GIATA ID.
On hotel data ingestion from any supplier, extract the supplier's property ID and look up the corresponding GIATA ID via the multi-codes API or flat-file lookup; store the GIATA ID as your canonical identifier.
When combining rates from multiple suppliers for the same property, join records by GIATA ID rather than by name string matching to avoid duplicate display of the same hotel.
Fetch hotel descriptive content (name, address, coordinates, star rating, amenities) from GIATA's property content endpoint using the GIATA ID as the single source of truth.
When a new supplier is onboarded, run their property list through the GIATA lookup to build the ID mapping table before any live rate matching.
Handle unmapped properties (those with no GIATA ID) with a fallback name-and-address fuzzy match process, flagging them for manual review.
Known gotchas
Not all properties have GIATA IDs — budget properties, aparthotels, and new openings may be absent; your system must handle ungapped properties without crashing.
GIATA multi-codes data requires a licensed subscription and has terms restricting redistribution; ensure your data licensing agreement covers your use case.
Supplier property IDs change over time due to re-contracting or system migrations; run periodic reconciliation jobs to catch ID drift rather than assuming the mapping is static.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?