Travel, fares and hospitality rates
Fares and room rates move constantly and are almost never archived, so the history has to be collected as it happens. These sources cover the price side of travel — flights, hotels, fuel and the destinations they connect — as rows you can store and compare over time.
23 documented jobs across 5 sources.
Google Flights API
One-way, round-trip and multi-city itineraries with prices, stops and airline detail.
- Alerting on a price threshold
- Building historical airfare series
- Corporate travel benchmarking
- Fare monitoring on a fixed route
- Route and competition analysis
- Travel-app price comparison
Google Flights API — parameters, schema and worked examples →
Google Flights Deals API
Google Flights Deals API - the 30 cheapest destinations from any airport as structured JSON, each flagged when it beats its route's typical price.
- Build your own fare history by scheduling runs and storing the rows
- Feed a price-alert product with the underlying fare data
- Fill a fare newsletter with destinations that genuinely beat their typical price
Google Flights Deals API — parameters, schema and worked examples →
Fuel Prices API
Live per-station pump prices by ZIP, city or coordinates, across six fuel grades.
- Building historical price time series
- Fleet and route-planning cost models
- Metro-level pump price monitoring
- Powering a price-comparison app
- Procurement benchmarking
Agoda Hotel API
Per-room hotel rates for one stay, with pre-discount price and cancellation terms on every offer.
- Finding refundable and free-cancellation hotel rates
- Hotel rate monitoring for a specific stay
- Hotel rate parity checks against a direct channel
- Measuring how deep an advertised hotel discount really is
Google Hotels API
Hotel search, property details, photos and reviews, with price and rating filters.
- Hotel rate monitoring for a compset
- Market entry research for a new location
- Revenue management benchmarking
- Travel-app inventory and pricing
- Vacation rental supply analysis
Google Hotels API — parameters, schema and worked examples →