This guide walks you through the core Mapping.Travel API workflow: authenticate, upload an inventory file, start a mapping job, poll for completion, and retrieve your matched results. By the end you will have a working end-to-end integration you can adapt to your own data pipeline.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.
Prerequisites
- A Mapping.Travel account with an API token (see Authentication)
curlor any HTTP client- A hotel inventory file in CSV, JSON, Excel (.xlsx), or Parquet format
Get your Bearer token
Retrieve your API token from Settings → API tokens in the Mapping.Travel dashboard. You will use it in every request below.Set it as an environment variable so you do not have to repeat it:
Prepare your inventory file
Your inventory file must include hotel records with enough information for matching. For CSV, use the following columns:
Example CSV:
| Column | Required | Description |
|---|---|---|
id | Yes | Your internal hotel identifier |
name | Yes | Hotel name |
address | No | Street address |
city | Yes | City name |
country | Yes | ISO country code (e.g. US, FR) |
latitude | No | Decimal latitude |
longitude | No | Decimal longitude |
JSON, Excel (.xlsx), and Parquet files are also accepted. The column names must match the schema above regardless of format.
Upload your inventory
POST your file to If you are mapping against a specific supplier’s ID space (for A successful upload returns Save the
/api/v1/inventory. The API accepts multipart/form-data.ID_TO_ID or HYBRID mode), include the supplierCode parameter:201 Created with an uploadId:uploadId—you need it in the next steps.Uploads are idempotent. If you upload the same file twice, the API returns the same
uploadId.Start a mapping job
POST to A successful response returns
/api/v1/mapping with the partnerInventoryId from your upload. Choose a mode that matches your use case:STANDARD— fuzzy matching by name and location (recommended for most cases)ID_TO_ID— match by supplier hotel ID (requires asupplierCodeon the upload)HYBRID— try ID-based match first, fall back to fuzzy
201 Created with a mappingJobId:Check mapping status
Mapping jobs run asynchronously. Poll While running:When complete:
GET /api/v1/mapping/{mappingJobId} until status is COMPLETED or FAILED.Retrieve your mapping results
Once the job is The response includes each partner hotel alongside its matched reference hotel:Hotels with no match are included with
COMPLETED, search the results by POSTing to /api/v1/mapping/{mappingJobId}/results/search. You can filter by hotel name, city, country, partner ID, or matched reference ID.matchedReferenceHotelId: null and matchMethod: null.Next steps
Inventory uploads
Manage uploads, list past inventories, and download files.
Mapping modes
Learn when to use STANDARD, ID_TO_ID, and HYBRID modes.
Billing and usage
Monitor quota usage and manage your subscription.
API reference
Full reference for all endpoints, parameters, and response shapes.