Newgoogle-apiplugins
Structured Google plugins for search, shopping, and maps
View as MarkdownOne managed endpoint per Google surface (search, shopping, maps, and more), returning JSON instead of HTML.
The Google Scraper API now covers seven Google surfaces, each as a dedicated plugin returning parsed JSON. No HTML parsing, no JavaScript rendering, no protobuf decoding on your end.
What's covered
| Sub-API | Endpoint | What it returns |
|---|---|---|
| Search | /plugin/google/search | Organic results, ads, knowledge graphs, local packs, related questions |
| Maps | /plugin/google/maps | Places, place details, paginated reviews, popular times, owner responses |
| Shopping | /plugin/google/shopping | Up to 40 products with prices, retailers, ratings, delivery info |
| Flights | /plugin/google/flights | Fares, layovers, durations, airlines, carbon emissions, price history |
| Hotels | /plugin/google/hotels | Listings with ratings, class, amenities, GPS, images |
| News | /plugin/google/news | Articles with direct publisher URLs, ISO dates, bylines |
| Trends | /plugin/google/trends | Interest over time, by region, related queries, real-time trending |
Why it matters
- Shared vocabulary: every sub-API uses the same
hl(150+ languages),gl(240+ countries),google_domain(84 domains) parameters, so localization works the same everywhere. - Chained identifiers: a
place_idfrom Search flows to Maps Place and Maps Reviews; atopic_tokenfrom News works across drivers;data_idchains between Maps endpoints. - Async-compatible: every endpoint is also available through the Async API with plugins for bulk runs.
Most endpoints cost 10 credits per request, with single-credit exceptions noted on each sub-API page. See the Google Scraper API overview to pick a starting point.
