Google Events API - Access Google Events Data
Pricing
Pay per event
Google Events API - Access Google Events Data
Extract event data from Google Events including titles, dates, locations, ticket information, and venue details. Supports advanced filtering (date ranges, virtual events), localization (country/language), and pagination. Structured JSON for event discovery, market research, and event platforms.
Pricing
Pay per event
Rating
5.0
(4)
Developer

John
Actor stats
4
Bookmarked
7
Total users
4
Monthly active users
7 hours ago
Last modified
Categories
Share
π Google Events Search Scraper
The most powerful, reliable, and feature-rich Google Events search scraper for Apify
π‘ What is Google Events Search Scraper?
A Google Events Search Scraper is a smart automation tool that helps you extract event listings, dates, locations, ticket information, and detailed event data from Google Events β all in structured data formats like JSON, CSV, or Excel.
This scraper lets you turn Google Events' vast database into a valuable dataset for event discovery, market research, competitive analysis, or event planning. Whether you're building event discovery platforms, monitoring event trends, conducting market analysis, or creating event aggregation applications, you'll gain actionable insights fast β‘.
β SEO Benefit: By using structured Google Events data, businesses can optimize event listing pages, monitor competition, and create data-rich content that boosts organic visibility.
π¦ What Data Can You Extract with Google Events Scraper?
| π·οΈ Data Type | π Description |
|---|---|
| π Event Details | Event title, description, dates, times, and links |
| π Date & Time Info | Start dates, event duration, "when" descriptions |
| π Location Data | Event addresses, venue information, location maps |
| π« Ticket Information | Ticket sources, links, ticket providers (Ticketmaster, Eventbrite, etc.) |
| ποΈ Venue Details | Venue name, ratings, reviews, venue links |
| πΊοΈ Location Maps | Map images and links to event locations |
| π― Hit Chips | Filter chips available in search results (date filters, event types) |
| π Search Filters | Available filter options for refining searches |
| π Search Metadata | Total results, pages processed, pagination info |
This structured Google Events dataset can be exported for analysis, visualization, or integration into your event discovery and planning workflows.
βοΈ Key Features of Google Events Scraper
β¨ Comprehensive Data Coverage β Extract every essential data field: event titles, descriptions, dates, locations, ticket info, and venue details.
π Advanced Filtering β Filter by date ranges (today, tomorrow, week, weekend, month), event types (virtual events), and combine multiple filters for precise results.
π Localization Support β Search in different countries and languages with support for localized event results.
π Intelligent Pagination β Automatic handling of pagination with support for fetching multiple pages of results.
π― Hit Chips Support β Use advanced filters (hit chips) like date:today, date:week, event_type:Virtual-Event to refine your searches.
π° Cost-Effective Pricing β Pay only for what you use with transparent per-page pricing. No hidden fees or monthly subscriptions.
π‘οΈ Enterprise-Grade Reliability β Built for developers and businesses who demand reliability. Comprehensive error handling, robust logging, and production-ready code.
π¦ Structured Output β Clean, structured JSON output ready for immediate use in your applications.
π Usage Examples
Example 1: Basic Search (Events in New York)
Search for events with a simple query.
{"q": "events in New York","max_pages": 1}
Example 2: Search with Location and Localization
Search for events with geographic location and language preferences.
{"q": "concerts","location": "Austin, Texas, United States","gl": "us","hl": "en","max_pages": 1}
Example 3: Search with Single Hit Chip (String)
Search for today's events using a date filter.
{"q": "sports events","location": "Los Angeles, CA","advanced": "date:today","max_pages": 1}
Example 3b: Search with Comma-Separated Hit Chips (String)
Search for today's virtual events using multiple filters.
{"q": "concerts","advanced": "event_type:Virtual-Event,date:today","max_pages": 1}
Example 3c: Search with List of Hit Chips
Search using a list of advanced filters.
{"q": "conferences","advanced": ["date:today", "event_type:Virtual-Event"],"max_pages": 1}
Example 4: Pagination (Multiple Pages)
Search across multiple pages to get more results.
{"q": "music festivals","location": "California, United States","gl": "us","hl": "en","max_pages": 2}
Example 5: Comprehensive Search (All Parameters + Advanced Filters)
Search with all available parameters including location, localization, and advanced filters.
{"q": "theater shows","location": "New York, NY","gl": "us","hl": "en","advanced": ["date:month", "event_type:Virtual-Event"],"max_pages": 2}
π Input Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
q | string | β Yes | - | Search query string (e.g., "concerts in New York", "sports events", "theater shows"). Required. |
location | string | β | - | Geographic location for localized event results (e.g., "Austin, Texas, United States", "New York, NY"). Optional. Helps narrow down events to a specific area. |
gl | string | β | - | Country code for localization (ISO 3166-1 alpha-2, lowercase). Optional. Defaults based on search context if not specified. See Country Codes section below for complete list. |
hl | string | β | - | Language code for localization (ISO 639-1, lowercase). Optional. Defaults based on country if not specified. See Language Codes section below for complete list. |
advanced | string or array | β | - | Advanced filters (hit chips). Can be a single filter string, comma-separated string, or array of strings. Optional. See Advanced Filters (Hit Chips) section below for available options. |
max_pages | integer | β | 1 | Maximum number of pages to fetch. Set to 0 for no limit (fetch all available pages). Default: 1. Each page is charged separately at $0.02 per page. |
output_file | string | β | Auto-generated | Optional filename to save results as JSON. If not provided, will auto-generate based on query and timestamp. |
π Country Codes (gl parameter)
The gl parameter accepts ISO 3166-1 alpha-2 country codes (lowercase). Here are the most common options:
| Code | Country | Code | Country | Code | Country |
|---|---|---|---|---|---|
us | United States | uk | United Kingdom | ca | Canada |
au | Australia | de | Germany | fr | France |
it | Italy | es | Spain | nl | Netherlands |
be | Belgium | at | Austria | ch | Switzerland |
se | Sweden | no | Norway | dk | Denmark |
fi | Finland | pl | Poland | cz | Czech Republic |
ie | Ireland | pt | Portugal | gr | Greece |
hu | Hungary | ro | Romania | bg | Bulgaria |
hr | Croatia | sk | Slovakia | si | Slovenia |
ee | Estonia | lv | Latvia | lt | Lithuania |
jp | Japan | kr | South Korea | cn | China |
tw | Taiwan | hk | Hong Kong | sg | Singapore |
my | Malaysia | th | Thailand | id | Indonesia |
ph | Philippines | vn | Vietnam | in | India |
pk | Pakistan | bd | Bangladesh | lk | Sri Lanka |
nz | New Zealand | za | South Africa | br | Brazil |
mx | Mexico | ar | Argentina | cl | Chile |
co | Colombia | pe | Peru | ve | Venezuela |
π Language Codes (hl parameter)
The hl parameter accepts ISO 639-1 language codes (lowercase). Here are the most common options:
| Code | Language | Code | Language | Code | Language |
|---|---|---|---|---|---|
en | English | es | Spanish | fr | French |
de | German | it | Italian | pt | Portuguese |
ru | Russian | ja | Japanese | ko | Korean |
zh | Chinese | zh-cn | Chinese (Simplified) | zh-tw | Chinese (Traditional) |
ar | Arabic | hi | Hindi | th | Thai |
vi | Vietnamese | id | Indonesian | ms | Malay |
tl | Filipino | nl | Dutch | pl | Polish |
tr | Turkish | cs | Czech | sv | Swedish |
da | Danish | fi | Finnish | no | Norwegian |
hu | Hungarian | ro | Romanian | bg | Bulgarian |
hr | Croatian | sk | Slovak | sl | Slovenian |
et | Estonian | lv | Latvian | lt | Lithuanian |
el | Greek | he | Hebrew | fa | Persian |
ur | Urdu | bn | Bengali | ta | Tamil |
te | Telugu | ml | Malayalam | kn | Kannada |
gu | Gujarati | pa | Punjabi | mr | Marathi |
π― Advanced Filters (Hit Chips)
The advanced parameter accepts hit chips (filter chips) that appear in Google Events search results. You can use:
Date Filters
| Filter | Description |
|---|---|
date:today | Events happening today |
date:tomorrow | Events happening tomorrow |
date:week | Events happening this week |
date:weekend | Events happening this weekend |
date:next_week | Events happening next week |
date:month | Events happening this month |
date:next_month | Events happening next month |
Event Type Filters
| Filter | Description |
|---|---|
event_type:Virtual-Event | Virtual/online events only |
Using Multiple Filters
You can combine multiple filters in three ways:
-
Single string with comma separation:
{"advanced": "event_type:Virtual-Event,date:today"} -
Array of strings:
{"advanced": ["date:today", "event_type:Virtual-Event"]} -
Single filter as string:
{"advanced": "date:today"}
Example Use Cases:
"date:today"- Find all events happening today"event_type:Virtual-Event"- Find all virtual events"event_type:Virtual-Event,date:today"- Find today's virtual events["date:week", "event_type:Virtual-Event"]- Find this week's virtual events
π Output Format
Dataset Item Structure
Each page of results is pushed as a separate dataset item with the following structure:
{"search_parameters": {"q": "events in New York","location": null,"gl": null,"hl": null,"start": null,"advanced": null,"max_pages": 1,"applied_hit_chips": null},"search_metadata": {"total_results": 10,"events_count": 10,"hit_chips_count": 0,"filters_count": 0,"pages_processed": 1,"max_pages_set": 1,"pagination_limit_reached": true},"search_timestamp": "2025-12-13T10:30:00.123456","page_number": 1,"events": [{"title": "Funk Tribu","date": {"start_date": "Nov 14","when": "Fri, Nov 14, 10 PM β Sat, Nov 15, 1 AM"},"address": ["Avant Gardner, 140 Stewart Ave","Brooklyn, NY"],"link": "https://open.spotify.com/concert/5FXK8DRwn1wnBPbdW6r7hb","event_location_map": {"image": "https://www.google.com/maps/vt/data=...","link": "https://www.google.com/maps/place/..."},"description": "Find tickets for Funk Tribu at Park Slope Brooklyn Warehouse in New York City on 11/14/2025 at 10:00 PM","ticket_info": [{"source": "Spotify.com","link": "https://open.spotify.com/concert/...","link_type": "tickets"},{"source": "Ticketmaster.com","link": "https://ticketmaster.com/...","link_type": "tickets"}],"venue": {"name": "Avant Gardner","rating": 4.1,"reviews": 4378,"link": "https://www.google.com/search?q=Avant+Gardner&..."}}],"hit_chips": [],"filters": []}
Output Fields
search_parameters: Complete search configuration used for the querysearch_metadata: Summary statistics about the search results including total results available, pages processed, and pagination statussearch_timestamp: ISO timestamp when the search was performedpage_number: Current page number (1-indexed)events: Array of event listings with comprehensive detailshit_chips: Available filter chips from search results (typically on first page only)filters: Available filter options for the search query (typically on first page only)
Event Fields
Each item in events contains:
title: Event title/namedate: Event date information includingstart_dateandwhen(formatted date/time string)address: Array of address lines for the event locationlink: Direct link to the event pageevent_location_map: Map image URL and link to Google Maps locationdescription: Event descriptionticket_info: Array of ticket sources with links and link types (tickets, more info, etc.)venue: Venue information including name, rating, reviews, and venue link
π― Use Cases
- Event Discovery: Find events matching specific criteria (location, date, type)
- Market Research: Analyze event trends, popularity, and availability across different locations
- Competitive Analysis: Monitor event listings, pricing, and ticket availability
- Event Aggregation: Build event discovery platforms and aggregators
- Data Analytics: Collect event data for business intelligence and analysis
- Event Planning: Research events for personal or business planning
- Lead Generation: Identify popular events and trending venues for business opportunities
- Content Creation: Gather event data for content marketing and SEO
- Virtual Event Discovery: Find and track virtual/online events using
event_type:Virtual-Eventfilter
β Frequently Asked Questions
Q1. How do I get started with Google Events Scraper?
Simply provide a q (search query) parameter with your search term, then run the Actor. The scraper will automatically extract event data and return structured JSON results.
Q2. Is the search query (q) parameter required?
Yes, the q parameter is required. You must provide a search query to search for events.
Q3. Can I filter results by date?
Yes! Use the advanced parameter with date filters like date:today, date:week, date:month, etc. See the Advanced Filters (Hit Chips) section above for all available date filters.
Q4. How do I search for virtual events?
Use the advanced parameter with event_type:Virtual-Event. You can combine it with date filters: "event_type:Virtual-Event,date:today" to find today's virtual events.
Q5. Can I use multiple filters at once?
Yes! You can combine multiple filters by:
- Using comma-separated string:
"event_type:Virtual-Event,date:today" - Using an array:
["date:today", "event_type:Virtual-Event"]
Q6. How does pagination work?
The scraper automatically handles pagination. Set max_pages to control how many pages to fetch:
max_pages: 1(default) - Fetch only the first pagemax_pages: 5- Fetch up to 5 pagesmax_pages: 0- Fetch all available pages (no limit)
Each page is charged separately.
Q7. Can I search in different countries and languages?
Yes! Use the gl (country code) and hl (language code) parameters for localization. See the Country Codes and Language Codes sections above for available options.
Q8. What data format does the scraper return?
The scraper returns structured JSON data with event details, dates, locations, ticket information, and metadata. Results are automatically cleaned and validated for schema compliance.
Q9. Can I export the data?
Yes! Results are stored in Apify's dataset format and can be exported as JSON, CSV, Excel, or accessed via API.
Q10. How do I use the location parameter?
The location parameter helps narrow down events to a specific geographic area. Examples: "Austin, Texas, United States", "New York, NY", "Los Angeles, CA".
Q11. What happens if my search returns no results?
If a search returns no events, the events_count in search_metadata will be 0, and the events array will be empty. The Actor will still complete successfully and return the search metadata.
π Technical Notes
- Results are sorted by relevance by default (Google Events API default)
- The
qparameter is required and must be a non-empty string - Date filters in
advancedparameter use Google's predefined date ranges (today, week, month, etc.) - Each page is pushed as a separate dataset item for accurate per-page billing
- Results are automatically cleaned and validated to ensure JSON-serializable output
- The
max_pagesparameter controls how many pages to fetch. Set to0for no limit (fetch all available pages) - The
advancedparameter accepts strings, comma-separated strings, or arrays of strings - Location and localization parameters (
location,gl,hl) are optional but recommended for better results - Event data includes ticket information from multiple sources (Ticketmaster, Eventbrite, Spotify, etc.)
- Venue information includes ratings and reviews when available
π Ready to Collect Google Events Data?
Start using Google Events Search Scraper today and transform public event listings into actionable insights. Whether you're building event discovery platforms, monitoring event trends, conducting market research, or creating event aggregation applications, you'll have clean, structured data in minutes!
Made with β€οΈ
Transform your event search automation with the most reliable and feature-rich Google Events scraper on Apify.
Last Updated: 2025.11.17