← ClaudeAtlas

apify-google-flights-apilisted

Use Google Flights as an API with the Apify Google Flights Actor (johnvc/Google-Flights-Data-Scraper-Flight-and-Price-Search). There is no official google flights api, so this skill fills the gap. Give departure and arrival airport codes plus dates, and get structured flight results as JSON, one row per flight with price, currency, airlines, departure and arrival times, stops, layover airports, duration, travel class, and flight numbers, plus price insights for the route. Supports one-way, round-trip, and multi-city itineraries, 29 languages, 39 countries, and filters for price, stops, and airlines. Use when the user wants a google flights api, to scrape google flights, a google flights scraper, flight results as JSON or CSV, or airfare data for a route by API or Python. Pay-per-page billing, MCP-ready for Claude and other AI agents.
johnisanerd/claude-skill-google-flights-api · ★ 0 · Data & Documents · score 66
Install: claude install-skill johnisanerd/claude-skill-google-flights-api
# Google Flights API: Structured Flight Search Results Use Google Flights as an API. There is no official Google Flights API, so developers scrape it; this Actor does that as a hosted service. Route and dates in, structured JSON out: one row per flight with price, airlines, times, stops, and duration, plus route-level price insights. ## When to use this skill - The user wants a "Google Flights API" (none exists officially; the predecessor QPX Express shut down in 2018). - They want to scrape Google Flights results for a route into JSON or CSV. - They want airfare data by API or from Python for a travel app, dataset, or analysis. - They ask for a "Google Flights scraper" or "how to scrape Google Flights". Not for: live aircraft tracking or flight status (this is a fare and search scraper, not a radar), creating reservations (it returns booking links, not tickets), or hotel searches (use the Google Hotels Actor). ## What you get (one dataset item per page, flights nested in `all_flights`) Each dataset item is one page of results holding an `all_flights` array (about 30 flights per page). Per flight: `price`, `currency`, `route`, `airlines`, `airline_logo`, `departure_airport`, `departure_time`, `arrival_airport`, `arrival_time`, `stops`, `stops_label`, `layover_airports`, `duration`, `duration_minutes`, `travel_class`, `flight_numbers`, `overnight`, `often_delayed`, `carbon_emissions_g`, `booking_token`, `category`. The item also carries `best_flights` and `other_flights`