Skip to main content
Every S3 and SFTP delivery writes one file per completed mapping job. The file contains the matched hotel records for that job in the format configured for your organization.

File naming pattern

mapping_results_{partnerInventoryId}_{yyyy-MM-dd}.{ext}
SegmentExampleDescription
partnerInventoryIdINV-20240601-ACMEThe partnerInventoryId from the inventory upload
yyyy-MM-dd2026-06-07UTC date the mapping job completed
extcsv, json, xlsxDetermined by your export format config
Example filenames:
  • mapping_results_INV-20240601-ACME_2026-06-07.csv
  • mapping_results_spring-catalog_2026-06-07.json
  • mapping_results_Q2-hotels_2026-06-07.xlsx
If two jobs for the same inventory complete on the same UTC date, the second delivery overwrites the first for S3 and SFTP destinations. Use a pathPrefix with date hierarchy (e.g. results/2026/06/07/) or switch to webhook delivery if you need every result preserved.

Supported formats

CSV

UTF-8, comma-delimited by default. Header row included. Delimiter and header presence are configurable. Suitable for spreadsheets and most ETL tools.

JSON

A JSON array of result objects. One file per job. Easy to parse with any language; suitable for API-style consumers.

XLSX

Excel 2007+ workbook. Single sheet named Results. Useful for business stakeholders who work in spreadsheet tools.
Configure your format with PUT /api/v1/export-format. See the export format API reference for field options including compression (gzip or none) and includeFields.

Column reference

All three formats contain the same columns (unless you restrict them with includeFields):
ColumnTypeDescription
mappingJobIdstring (UUID)ID of the mapping job that produced this row
partnerInventoryIdstringInventory identifier from the upload
supplierHotelIdstringYour internal hotel identifier from the inventory row
referenceHotelIdstringMapping.Travel’s canonical hotel ID
referenceNamestringCanonical hotel name
referenceCountryCodestringISO 3166-1 alpha-2 country code
referenceCitystringCity name from the reference database
confidencenumber (0–1)Match confidence score
matchMethodstringAlgorithm that produced the match (EXACT, FUZZY, MANUAL, etc.)
statusstringMATCHED, UNMATCHED, or PENDING_REVIEW
supplierIdstringMapping.Travel supplier ID (if matched to a specific supplier)
supplierNamestringSupplier display name
exportedAtstring (ISO 8601)UTC timestamp when this row was written to the file

CSV example

mappingJobId,partnerInventoryId,supplierHotelId,referenceHotelId,referenceName,referenceCountryCode,referenceCity,confidence,matchMethod,status,supplierId,supplierName,exportedAt
job_01HZ,INV-ACME,ACME-001,ref_4892,Hilton London Bankside,GB,London,0.97,EXACT,MATCHED,sup_hilton,Hilton Hotels,2026-06-07T12:00:00Z
job_01HZ,INV-ACME,ACME-002,ref_1034,The Savoy,GB,London,0.91,FUZZY,MATCHED,sup_fairmont,Fairmont,2026-06-07T12:00:00Z
job_01HZ,INV-ACME,ACME-099,,,,0,,UNMATCHED,,2026-06-07T12:00:00Z

JSON example

[
  {
    "mappingJobId": "job_01HZ",
    "partnerInventoryId": "INV-ACME",
    "supplierHotelId": "ACME-001",
    "referenceHotelId": "ref_4892",
    "referenceName": "Hilton London Bankside",
    "referenceCountryCode": "GB",
    "referenceCity": "London",
    "confidence": 0.97,
    "matchMethod": "EXACT",
    "status": "MATCHED",
    "supplierId": "sup_hilton",
    "supplierName": "Hilton Hotels",
    "exportedAt": "2026-06-07T12:00:00Z"
  }
]