Skip to main content
The Google Events API allows users to retrieve information about events based on specified search terms, locations, and various filter options.

​
Get Your API Key

Sign in at hasdata.com, go to your account settings, and copy your API key. All requests must include your key in the x-api-key header.

​
Request Cost and API Credits

Each request to the Google Events API consumes API Credits from your account balance.
  • Cost per request: 5 API Credits
  • Credits are deducted only for successful requests.
  • Your total available credits depend on your active plan.
You can use your credits across all HasData APIs. The same credit balance is shared platform-wide.
Unused credits do not roll over. Any remaining credits expire at the end of the current billing period.
To monitor your credit usage and remaining balance, sign in to your account dashboard at app.hasdata.com.

​
Make Your First Request

curl --request GET \
  --url 'https://api.hasdata.com/scrape/google/events?q=Events%20in%20New%20York&location=Austin%2CTexas%2CUnited%20States' \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <your-api-key>'

​
API Parameters

ParameterDefault ValueRequiredDescription
qEvents in New YorkYesSpecify the search term for which you want to scrape the SERP.
locationAustin,Texas,United StatesNoGoogle canonical location for the search.
uule-NoThe encoded location parameter.
domain-NoGoogle domain to use. Default is google.com.
gl-NoThe two-letter country code for the country you want to limit the search to.
hl-NoThe two-letter language code for the language you want to use for the search.
start-NoThis parameter specifies the number of search results to skip and is used for implementing pagination. For example, a value of 0 (default) indicates the first page of results, 10 refers to the second page, and 20 to the third page.
htichips-NoFilter parameter for refining event search results. Supports various filters for events. Multiple filters can be passed using a comma. The available filters are:

- date:today: Today’s Events
- date:tomorrow: Tomorrow’s Events
- date:week: This Week’s Events
- date:weekend: This Weekend’s Events
- date:next_week: Next Week’s Events
- date:month: This Month’s Events
- date:next_month: Next Month’s Events
- event_type:Virtual-Event: Online Events

For example, to filter for today’s online events, use: event_type:Virtual-Event,date:today.