The Google Events API searches the events vertical — 'concerts in Milan', 'tech meetups in Berlin', 'food festivals near me' — and returns each event card as a structured row: title, the date line as shown, venue, address, link and thumbnail. It is the SERP block turned into rows you can drop into a calendar or a listings page.
Google assembles this vertical service-side from across the web, so one query surfaces events from dozens of ticketing and venue sites at once without you integrating any of them. Each run returns up to 20 event cards for the country and lang you ask for, read over the request tier with no browser. What you get is exactly what Google chooses to show a searcher in that locale — the same curation, delivered as data.
$0.002 per delivered event, up to 20 events per run. Nothing delivered means nothing charged.
You send a query describing the events you want, optionally a location to search as if from a specific place, plus country/lang and a max_results up to 20. The collector reads the rendered events vertical through an in-region exit and flattens each card.
Worth knowing before you build on it:
date comes back the way Google prints it — 'Sat, Aug 22, 7 – 10 PM' — because that is what the card carries; parse it against the event's locale, not a fixed format.location and country together decide which local events appear; the same query from Milan and from Berlin returns different cards.query is required — the event search itself. location lets you search as if from a named place, which matters for 'near me'-style intent; country and lang set the exit and Google's gl/hl. max_results caps delivery at 20, the depth of the vertical.
Each event is one flat row: title, date (the date line verbatim), venue, address, link to the event and thumbnail. Fields Google omits on a given card come back null rather than guessed — a card without a printed address returns an empty address, not an invented one.
$0.002 per delivered event ($2 per 1,000). Nothing delivered means nothing charged, and the $2 monthly free credit covers roughly 1,000 events here. Volume tiers take up to 30% off.
$0.002 per delivered event, $2 per 1,000. A single query returns up to 20 cards, so a search costs about four cents at most. Monitoring a city's calendar by re-running a handful of queries daily is a few dollars a month, not a platform integration.
The $2 monthly allowance (no card) covers about 1,000 delivered events, and volume tiers take up to 30% off. GET /v1/scraper/collectors returns the exact price your key pays.
Google has no official events API. The events vertical is a search feature, not a developer product — there is no documented endpoint, no key to request and no support channel for it. Event data on the web is otherwise scattered across ticketing platforms, each with its own API, coverage and terms.
This collector reads the aggregated vertical Google already built, so one call spans the sources Google spans. It returns what the card shows and nothing it does not: there is no attendee count, no ticket inventory and no organiser contact in a Google event card, so none appears here. For anything structured beyond the card, you would go to the specific ticketing source.
The events vertical is a rendered SERP feature, which makes DIY collection harder than a plain page fetch:
country and location.venue or date fields silently. Ours is maintained against those changes.To keep your own scraper and just run it on dependable in-country exits, that network is our residential proxies.
Populate a what's-on page by re-running a set of city queries on a schedule. Each card already carries venue, address and link — enough for a listing without touching a ticketing API.
Track concerts, conferences or festivals in your target cities and time campaigns or inventory around them. The date line tells you when demand will spike locally.
Watch which events surface for a venue or category over time by diffing the returned cards, spotting new bookings as Google starts showing them.
One run returns up to 20 event cards for one query and locale — the depth Google exposes in the vertical, not a cap we add. The data is exactly what the card prints: title, date line, venue, address, link, image. There is no ticket price, seat availability or attendee figure, because the card does not carry them, and this collector will not invent them. Runs are independent and parallelise up to your plan's rate limit — 60 a minute on pay-as-you-go, up to 1,200 on the top tier.
Legally: the vertical is public and reading public data is broadly lawful, but Google's terms restrict automated access and rules vary by country. Background, not legal advice.
$2 of usage a month with no card, which at $0.002 per event is about 1,000 delivered events. Google offers no official events API at any price, so this free allowance is not competing with a first-party tier.
No. Your QuantumProxies API key is the only credential — no Google Cloud project, no OAuth, no per-vertical registration, because the events vertical is not a keyed Google product.
$0.002 per delivered event, $2 per 1,000, no subscription. A query returns up to 20 cards, so a single search is at most about four cents. Volume tiers take up to 30% off, and GET /v1/scraper/collectors shows your key's live price.
No. A Google event card carries title, date, venue, address and a link — not ticket price, seat inventory or organiser contact. Those live on the ticketing site the link points to, and we return only what the card actually shows.