After starting a mapping job, use this endpoint to poll for its progress. The response includes the current status along with counts of matched, unmatched, and total hotels once the job has processed enough data to report them.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.
Request
UUID of the mapping job to retrieve. You receive this from the start mapping response.
Response
UUID of the mapping job.
Current status of the job.
| Value | Description |
|---|---|
PENDING | Job is queued and has not started yet. |
RUNNING | Job is actively processing hotels. |
COMPLETED | Job finished successfully. Results are available. |
FAILED | Job encountered an error and did not complete. |
Mapping mode used for this job:
STANDARD, ID_TO_ID, or HYBRID.Total number of hotels in the partner inventory. Available once the job begins processing.
Number of hotels successfully matched to a reference hotel. For
HYBRID jobs, this is the combined count of ID-to-ID and fuzzy matches.Number of hotels that could not be matched to any reference hotel.
UUID of the partner inventory being mapped.
ISO 8601 timestamp of when the job was created.
ISO 8601 timestamp of the last status update.
Error responses
| Status | Reason |
|---|---|
401 Unauthorized | Missing or invalid Authorization header. |
404 Not Found | No mapping job with the given ID exists for your organization. |
For
HYBRID mode jobs, the matchedCount reflects matches from both phases — ID-to-ID matches completed in phase 1 plus any additional fuzzy matches from phase 2. The job stays in RUNNING until both phases complete.