mocop
Browse · Docs · Guide · Analyze

FlightPowers Travel Data API

API by FlightPowers · rest

Live flight and hotel prices, and the context to judge them. Two data products behind one host: - Flights: live Google Flights searches. Every itinerary carries Google's own historical price band (price_insights_low/price_insights_high) and a low | typical | high verdict when Google shows one, plus a booking deep link. - Hotels: live Booking.com searches, including proxy_country (query from any market's viewpoint via residential proxies - the basis for rate-parity and geo-pricing monitoring). Auth: bring your own RapidAPI key; every request is billed to your own subscription. Subscribe at https://rapidapi.com/mtnrabi/api/google-flights-live-api/pricing (flights) or https://rapidapi.com/mtnrabi/api/booking-live-api/pricing (hotels). They are separate subscriptions. Honesty contract: flight searches report their own outcome in X-Search-Status (ok | empty | partial | degraded), so an empty array is never ambiguous. No uptime or latency figures are…

Endpoint: https://api.flightpowers.com/

Verification: observed. Source: crawl.

Capabilities (7)

  • Search one-way flights (live Google Flights results)
  • Search round-trip itineraries (paired legs priced together)
  • Look up one hotel by name: availability + price in one call
  • Resolve a hotel name to its Booking.com id
  • Room-level availability and pricing for one hotel
  • Search hotels at a destination
  • Check that an API key works as cheaply as possible
About · Contact · Privacy