hotel/request.json
{
"hotel_id": "source_hotel_id",
"check_in": "YYYY-MM-DD",
"check_out": "YYYY-MM-DD",
"occupancy": {
"adults": 2,
"rooms": 1
}
}Travel rate data · API delivery
Travel rates that arrive in your schema.
Hotel, flight, car rental, and activity prices from global OTA sources. Collected across web, app, and mobile web, and returned with the booking conditions that make them comparable.
hotel/response.json
{
"source": "supported_source",
"available": true,
"collected_at": "…",
"rooms": [{
"room_name": "…",
"rate_plans": [{
"total_price": "…",
"meal": "…",
"cancellation": "…"
}]
}]
}rate_plan fields
total_pricedecimal
taxesdecimal
mealstring
cancellationstring
payment_methodstring
collected_attimestamp
A hotel example. Fields, names, and response shape are specific to each product and source, and are agreed with you before launch.
Every request is defined by a confirmed source context, not by a product name alone.
productsourcepoint_of_salecurrencylanguagetravel_datestravellerschannel
Travel products
Four product lines. One delivery contract.
Available fields differ by product and by source. Each configuration is confirmed before launch.
Hotel rates
Query a hotel and stay. Receive the rooms, rate plans, prices, meals, cancellation terms, and payment methods the source displays.
Flight rates
Query a route and travel dates. Receive the fares the source displays for that search, with the conditions attached to each one.
Car rental rates
Query a pickup location and rental period. Receive the vehicle offers the source displays and the rental terms attached to them.
Activities and tickets
Query an activity and date. Receive the ticket and package options the source displays for that request.
From request to decision
Travel pricing data without a scraping stack.
You provide the product and query parameters. Datasynex handles collection and returns structured data for your own pricing, distribution, or analysis workflow.
Step 01
Define the query
Submit the source product ID, the travel dates, and the market or traveller parameters the source supports.
Step 02
Collect the offers
Datasynex visits the agreed source context and structures the offers available for that request.
Step 03
Use the context
Evaluate prices with their tax, inclusion, cancellation, payment, market, and collection context when available.
Sources and scale
Global OTA sources, three channels deep.
The same product can carry a different price on a source's website, its app, and its mobile web. Datasynex collects the channel your comparison depends on.
Collected daily10M+ records
ChannelsWeb · App · Mobile web
ProductsHotel · Flight · Car · Activities
Trip.comCtripAgodaand other global OTAs
Named sources are examples, not a fixed catalogue. Support is contracted per configuration — a named source does not imply every product, market, or channel.
Who it is for
Built for the teams that put travel prices inside their own product.
Datasynex is a data layer for systems, not a tool your analysts log into. There is no dashboard to adopt.
RMS and rate-shopping platforms
Ship competitor rates inside your own product without building and staffing a collection stack. The response arrives in the schema your pipeline already reads.
OTAs, metasearch, and wholesalers
Watch how your inventory is priced on the channels you compete on, and measure promotions and availability across sources on the same terms.
Travel agencies, TMCs, and corporate travel
Compare supplier prices for the trips you actually book, with the conditions attached so the cheapest result is the one you can hold.
Delivery
Choose delivery around the decision you need to make.
Coverage and available fields vary by product and source. Every pilot starts with an agreed product, source, market, query set, and response schema.
Real-Time Rate API
Request current rates for supported configurations using the source product ID and the travel dates.
Cached Rate API
Retrieve previously collected rates when predictable throughput matters more than a new source visit for every request. Each configuration runs on a collection schedule, and the cadence is set to match how often your decision changes.
Offer and Condition Data
Work with the offers displayed for the submitted query, together with the terms that make those offers comparable.
Lowest Bookable Rate
Derive the lowest rate only after aligning query conditions, currency, taxes, travellers, inclusions, cancellation, and collection time.
Built to your contract
The API is shaped around your system, not ours.
Four things are agreed during the pilot rather than handed to you fixed.
Response schema
Receive the fields your system needs, named and nested the way it already expects, instead of mapping our structure into yours after every response.
Sources and channels
Name the source, market, and channel your workflow depends on. A source that is not yet supported is scoped as part of the pilot rather than assumed.
Delivery and cadence
Choose request-time collection or scheduled collection, matched to how often the decision behind the data actually changes.
Dedicated endpoints
Move your comparison rules into the endpoint, so it returns the result your workflow acts on rather than raw offers your team has to post-process.
Use cases
One data layer. Four focused workflows.
Rate shopping
Track selected competitors across agreed sources, travel dates, and traveller conditions.
Revenue management
Feed current or scheduled competitor rates into your pricing models and analyst workflows.
Rate parity analysis
Compare source rates only after aligning query, currency, tax, inclusion, and market context.
Distribution analysis
Measure how offers, promotions, availability, and displayed prices vary across supported sources.
Start with a measurable pilot
Validate the data against the source pages you know.
Send the travel product, a representative query set, the source, the travel-date range, and your comparison rules. We will confirm the supported scope before proposing production access.