One of the world’s largest travel-experiences marketplaces
Uses competitive web data at millions of queries under a managed agreement.
Rates move by the minute. Parity breaks by the hour. See every rate, on every channel, for every night.
Import.io collects hotel rates, availability, fares, event demand and reviews from booking channels and travel sites. Revenue, distribution and intelligence teams receive structured data by stay date, channel and point of sale through an API, managed feed or Aperture.
| Property | Direct | Booking.com | Expedia | Google Hotels | Parity |
|---|---|---|---|---|---|
| Harbor View Hotel | $309 | $309 | $289 | $309 | Expedia −$20 |
| The Kestrel | $274 | $274 | $274 | $274 | ok |
| Northmoor Suites | $352 | $352 | $352 | $329 | metasearch −$23 |
| Brightwater Inn | $198 | $198 | $198 | $198 | ok |
| Seaport Grand | $415 | sold out | $429 | $415 | channel closed |
| Riverside Lofts | $231 | $231 | $231 | $231 | ok |
Production examples from organisations using Import.io today and in recent years.
Uses competitive web data at millions of queries under a managed agreement.
Runs a managed web data program that keeps expanding to new sources.
Has run competitive travel pricing on the Import.io platform.
A travel price is a function of stay date, length of stay, occupancy, point of sale, device and loyalty status. Change one and the answer changes. Import.io shops rates the way travellers actually search, across your channels and your competitors’, and tells you where parity broke before the booking goes elsewhere.
The same room has hundreds of prices depending on who asks, from where, for which nights. Rate shopping that ignores point of sale, occupancy or fees compares numbers that were never comparable — and misses the parity breaks that quietly send bookings to a channel you pay commission on.
Demand moves too: a concert, a conference or a cancelled flight changes the market in hours. We capture the rates and the signals together, on a budget planned around the stay dates that matter.
Six programs we run most often in this industry.
Related guidance: rate parity, price intelligence, availability data, reviews and ratings.
Your rates and your comp set’s, by channel, stay date, length of stay and occupancy, as total price.
ratesBreaks between direct, OTAs and metasearch detected and alerted, with the evidence captured.
parityEvents, conferences and ticket prices near your properties, so demand spikes show up before the pickup does.
demandAirline fares, bags and seat fees, car rental and tours by route, date and point of sale.
faresWhere your property ranks on each channel for key searches, and whether its content is right.
visibilityRatings and reviews across platforms, with topic-level sentiment on what guests praise and complain about.
reviews| field | type | example |
|---|---|---|
| property_id | str | harbor-view-bos |
| channel | enum | expedia |
| stay_date | date | 2026-11-14 |
| los | int | 1 |
| occupancy | str | 2 adults |
| room_type | str | King |
| rate_total | num | 289.00 |
| currency | str | USD |
| refundable | bool | true |
| point_of_sale | str | US |
| rank | int | 3 |
| retrieved_at | ts | 2026-09-25T16:02:40Z |
What breaks when this is done with scripts, and how Import.io handles it.
Stay dates × lengths of stay × occupancies × points of sale is millions of searches. Budgets are planned around the dates and markets where rates actually move.
Requests come from inside each market, so a US traveller’s price and a German traveller’s price are both captured as they are shown.
Rates, taxes and fees are captured separately and totalled, so nightly and total prices compare fairly across channels.
OTAs and metasearch run heavy anti-bot defences; rendering, fingerprints and challenges are handled inside the platform.
Same capture engine underneath each one.
Revenue and distribution teams who want rate shops and parity alerts delivered to their RMS or warehouse, under an SLA.
learn more →Hotel rates and event ticket listings, maintained and ready to trial.
learn more →Analysts who want to build their own rate and review extractors.
learn more →Programs collect publicly displayed rates, fares and reviews. No traveller accounts or booking data are involved; loyalty rates are captured only from accounts the customer owns and authorises.
Straight answers.
Stay date, length of stay, occupancy, room type, point of sale, currency and device, per channel.
As many as the program needs; most shop 90 to 365 days forward, with hourly refresh on near dates and daily on the rest.
Yes. Rates, taxes and fees are captured separately and totalled, so channels compare on what the traveller pays.
Yes. Breaks are detected per property, channel and date, and delivered as alerts with a captured snapshot as evidence.
Yes: airline fares and ancillaries by route and point of sale, and event ticket listings from secondary marketplaces.