Skip to main content
Suppliers are the travel platforms and OTAs, such as Expedia, Booking.com, Airbnb, Hotels.com, and Agoda, that maintain their own hotel databases with their own unique hotel IDs. When you connect a supplier to your mapping.travel account, you can use those supplier IDs to match hotels exactly rather than relying on fuzzy name and address comparison. This unlocks the ID-to-ID and Hybrid mapping modes, which are faster and more precise for inventory that includes supplier hotel IDs.

​
Supported suppliers

mapping.travel currently supports the following suppliers out of the box: Use GET /api/v1/suppliers to retrieve the current list of active suppliers. No authentication is required for this endpoint.

​
Why connect a supplier

Connecting a supplier does two things:
  1. It tells mapping.travel that your organization has a relationship with that platform and holds inventory with their hotel IDs.
  2. It enables you to start mapping jobs in ID_TO_ID or HYBRID mode against that supplier’s dataset.
Without a connected supplier, you can still run STANDARD fuzzy mapping on any inventory. Connecting a supplier is only required when you want to use supplier hotel IDs for matching.

​
How to connect a supplier

1

Find the supplier ID

Call GET /api/v1/suppliers to list all active suppliers and get their UUIDs.
2

Connect the supplier

Call POST /api/v1/suppliers/{supplierId}/connect with your API key. The supplier is linked to your organization immediately.
3

Upload inventory with supplierCode

When you upload your inventory file, pass the supplierCode parameter matching your supplier’s identifier (e.g., expedia). Each hotel record should include the supplier’s hotel ID in the supplierCode column.
4

Start a mapping job

Use ID_TO_ID or HYBRID mode when starting a mapping job against that inventory.

​
Viewing connected suppliers

Call GET /api/v1/suppliers/my-suppliers to see all suppliers currently connected to your organization.

​
Plan limits

Your plan grants a permanent budget of distinct suppliers: the total number of different suppliers your organization may ever connect. Connecting a supplier for the first time consumes one unit of that budget. The budget is not refunded when you disconnect, and reconnecting a supplier you have connected before is always free and does not count again. Your remaining budget is maxSuppliers minus the number of distinct suppliers you have ever connected. On a Basic plan (2 distinct suppliers), once you have connected two different suppliers you cannot connect a third — even after disconnecting one of them. Connecting a supplier beyond your budget returns a 409 Conflict. The GET /api/v1/suppliers/my-suppliers response includes a rateLimitRemaining field showing how much budget you have left.
Disconnecting and reconnecting cannot be used to cycle through different suppliers. Disconnecting frees the active connection but does not restore budget, so a Basic-plan organization is limited to the first two distinct suppliers it ever connects.
Disconnecting a supplier does not affect mapping jobs that have already completed. It only prevents new ID-to-ID or Hybrid mapping jobs from running against that supplier going forward.

​
Requesting a new supplier

If the supplier you need is not yet in the system, you can submit a request. Send a multipart request to POST /api/v1/suppliers/request with the supplier name, an optional description, an optional contact email, and a sample inventory file in CSV, JSON, or Excel format.
The request is accepted immediately (202) and reviewed by the mapping.travel team. Track your pending requests with GET /api/v1/suppliers/requests.