Supported suppliers
Mapping.Travel currently supports the following suppliers out of the box:| Supplier code | Platform |
|---|---|
expedia | Expedia |
booking | Booking.com |
airbnb | Airbnb |
hotels | Hotels.com |
agoda | Agoda |
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:- It tells Mapping.Travel that your organization has a relationship with that platform and holds inventory with their hotel IDs.
- It enables you to start mapping jobs in ID_TO_ID or HYBRID mode against that supplier’s dataset.
How to connect a supplier
Connect the supplier
Call
POST /api/v1/suppliers/{supplierId}/connect with your Bearer token. The supplier is linked to your organization immediately.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.Viewing connected suppliers
CallGET /api/v1/suppliers/my-suppliers to see all suppliers currently connected to your organization.
Plan limits
Your plan determines the maximum number of suppliers you can connect at once. If you reach your limit, connecting an additional supplier returns a400 error. Disconnect a supplier with DELETE /api/v1/suppliers/{supplierId}/disconnect to free up a slot.
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 toPOST /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.
202) and reviewed by the Mapping.Travel team. Track your pending requests with GET /api/v1/suppliers/requests.