Mapping.Travel is a hotel mapping API built for travel companies that need to reconcile partner hotel inventory against a global reference dataset. You upload your inventory, run a mapping job, and get back a structured set of matches—so you can deduplicate suppliers, normalize hotel data, and power downstream search and booking experiences.Documentation Index
Fetch the complete documentation index at: https://docs.mapping.travel/llms.txt
Use this file to discover all available pages before exploring further.
What you can do
The API covers the full mapping lifecycle: ingest raw inventory from any supplier, run configurable mapping jobs, query results, and export matched data for use in your systems.Quickstart
Upload your first inventory file and run a mapping job in under five minutes.
Authentication
Learn how to get your API token and authenticate every request.
Inventory uploads
Upload CSV, JSON, Excel, or Parquet files and track their processing status.
Mapping jobs
Start mapping jobs, choose a mapping mode, and retrieve matched results.
Key capabilities
Inventory ingestion. Upload hotel inventory in CSV, JSON, Excel (.xlsx), or Parquet format. Uploads are idempotent—sending the same file twice returns the same upload ID. Flexible mapping modes. Choose from three modes depending on your data:STANDARD— fuzzy name and location matching against the reference datasetID_TO_ID— match by supplier hotel ID when you have a known supplier codeHYBRID— combine ID-based and fuzzy matching in a single pass
expedia or booking) to enable ID-to-ID mapping against that supplier’s reference IDs.
Result export. After a mapping job completes, download the results or trigger a manual export for integration with downstream systems.
Billing and usage. Track mapping usage against your plan quota. Free plans include a daily mapping allowance; paid plans offer higher limits and credit-based overages.
Base URL
All API requests use the following base URL:/api/v1.