Product and source
Confirm the travel product, the source, and the available Web, App, or mobile collection context for the workload.
Coverage
Confirm the exact product and source before you build.
A listed source does not imply support for every product, country, point of sale, currency, device type, member state, or future date.
We contract coverage by product, source, and configuration, then test a representative query set against known source pages.
Query context
Confirm point of sale, currency, language, product mapping, travel dates, travellers, and other supported parameters.
Response contract
Confirm real-time or cached delivery, available fields, error states, source evidence, and collection time.
Sources
Global OTA sources, contracted per configuration.
Named sources are examples, not a fixed catalogue. A named source does not imply support for every product, market, or channel — the exact configuration is confirmed with you first.
Trip.comCtripAgodaand other global OTAs
Channels
One source can price the same product three ways.
Comparing a web price with an app price is not a like-for-like comparison. The channel is part of the agreed configuration.
Desktop website
The source's public site, collected in the point of sale, currency, and language you agree.
Native app context
App-only pricing and promotions, where the source runs them separately from its website.
Mobile browser
The mobile site, which can differ from both desktop and app for the same query.
Coverage dimensions
Know what must be confirmed before integration.
Coverage is defined by the source response and the agreed configuration. The endpoint contract is confirmed during the pilot.
| Dimension | What we confirm | Why it matters |
|---|---|---|
| Product and source | Travel product, source, and available Web, App, or mobile context | The same product can return different offers across source contexts. |
| Market and query | Point of sale, currency, language, device or member state, product mapping, travel dates, and the traveller parameters the source accepts | These conditions define which offers can be collected and compared. |
| Delivery and fields | Real-time or cached delivery, the offer fields, prices, taxes, inclusions, cancellation, payment, promotions, evidence, and collection time | Your application needs a known response schema and freshness rule. |
Comparison context
A price is useful only when its conditions travel with it.
Query
Product, travel dates, and the traveller parameters the source accepts.
Market
Point of sale, currency, language, device, and member context.
Offer
Inclusions, tax treatment, cancellation, payment, and promotion.
Evidence
Source URL, availability state, and collection time when available.
Pilot path
Move from a known page to a production contract.
Agree the product, source, market, query set, and fields.
Map each product to the source identifier.
Run representative queries and dates.
Review completeness, timing, errors, and evidence.
Confirm the production request and response contract.
Your coverage
Send the product and source you need to test.
We will confirm the supported request context and return structured samples for review against the source pages.