What does the TravelCore hotel booking API do?

The hotel API searches many supplier contracts through one request, returns properties already deduplicated by the mapping engine, and prices results with your own markup rules before they reach you. Booking requires an idempotency key. Suppliers that miss their time budget are named in the response instead of disappearing from it.

Hotels API — TravelCore.tech

Accommodation connectivity

Hotels API for travel teams

Multi-supplier accommodation search, booking and cancellation behind one contract.

Discuss this API View all APIs

Product overview

A clear contract for the next part of the journey.

The Hotels API is the centre of the platform. It fans a single search out to every connected supplier in parallel, maps the returned properties onto one TravelCore property object, applies your pricing rules, and returns a single ranked result set. Booking, modification and cancellation run through the same normalised surface, whichever supplier ultimately holds the reservation.

Coverage depends on your supplier agreements and the connections supported for your project. Markets, properties and rate access are reviewed during evaluation. TravelCore does not own hotel inventory; supplier coverage must be confirmed for your account.

ProductHotels

AvailabilityPartner evaluation

AuthenticationOAuth 2.0 client credentials

ContractHTTPS · JSON

What to review

Shape the integration around your operation.

Demonstrable for evaluation; integrations, project scope and launch readiness are agreed separately.

Capabilities

Parallel multi-supplier search with per-supplier timeout budgets
Unified property object across suppliers (mapping and deduplication)
Room, rate plan, board basis and occupancy normalisation
Structured cancellation policies with absolute deadlines, not prose
Pricing engine applied server-side: net, markup, commission, tax, fees
Multi-currency quoting with the FX rate stamped on the quote

Integration notes

Search returns as soon as the fastest suppliers answer. The default per-supplier budget is 6000 ms; suppliers that exceed it are reported as `timeout` in the response and the result set is marked `partial: true` rather than the whole call failing.
Rate-level content (photos of the exact room) varies by supplier and is passed through, not synthesised.
Modification support is supplier-dependent; where a supplier has no modify path, the API reports it rather than silently cancelling and rebooking.
Loyalty-rate and negotiated-corporate-rate access requires your own agreement with the supplier.

Endpoint reference

The hotels surface at a glance.

POST/v1/hotels/search

Fan out an availability search across every connected supplier and return one merged result set.

GET/v1/hotels/properties/{propertyId}

Full unified content for one property: description, amenities, images, geo, policies and room types.

POST/v1/hotels/rates/{rateId}/check

Re-validate a rate against the supplier immediately before payment, returning the binding price.

POST/v1/hotels/bookings

Create a booking against a checked rate.

GET/v1/hotels/bookings/{bookingId}

Retrieve a booking with its current status, policies and supplier reference.

POST/v1/hotels/bookings/{bookingId}/cancel

Cancel a booking and return the penalty actually applied by the supplier.

Need the complete contract?Review request fields, response schemas, authentication and launch requirements with the integration team.Discuss integration access