qstringrequired
Parameter defines the query you want to search. To search for events in a specific location, just include the location inside your search query (e.g. `Events in Austin, TX`).
Google Events
https://api.sandbase.ai/v1/api/google/eventsSearch events listed on Google by keyword and place, with title, date, venue, address, ticket links and thumbnails.
- Price
- $0.01USD / call
- Method
- POST
- Response
- JSON
- Parameters
- 1 required · 3 optional
Playground
Input
Parameter defines the query you want to search. To search for events in a specific location, just include the location inside your search query (e.g. `Events in Austin, TX`).
Parameter defines from where you want the search to originate. If several locations match the location requested, we'll pick the most popular one. Head to the /locations.json API if you need more precise control. The `location` and `uule` parameters can't be used together. It is recommended to specify `location` at the city level in order to simulate a real user’s search. If `location` is omitted, the search may take on the location of the proxy.
Parameter is the Google encoded location you want to use for the search. `uule` and `location` parameters can't be used together. Head to UULE Generator if you need to convert a location or GPS coordinates to `uule` parameter, and vice versa.
Parameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details.
OutputReady
Your output will appear here
Complete the inputs, then click Run.
API README
Google Events
Search events listed on Google by keyword and place, with title, date, venue, address, ticket links and thumbnails.
Request
curl -X POST "https://api.sandbase.ai/v1/api/google/events" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"q": "concerts in austin"}'
The result is returned in outputs[0].data as structured JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
q | string | Yes | Parameter defines the query you want to search. To search for events in a specific location, just include the location inside your search query (e.g. Events in Austin, TX). |
location | string | No | Parameter defines from where you want the search to originate. If several locations match the location requested, we'll pick the most popular one. Head to the /locations.json API if you need more precise control. The location and uule p |
uule | string | No | Parameter is the Google encoded location you want to use for the search. uule and location parameters can't be used together. Head to UULE Generator if you need to convert a location or GPS coordinates to uule parameter, and vice vers |
json_restrictor | string | No | Parameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details. |
Pricing
$0.010 per successful call. Failed calls are not charged.
Start building
Send your first request
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/google/events" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"q": "concerts in austin"
}
SANDBASE_JSON
)
printf '%s\n' "$result"2. Authentication
Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
3. Parameters
locationstring
Parameter defines from where you want the search to originate. If several locations match the location requested, we'll pick the most popular one. Head to the /locations.json API if you need more precise control. The `location` and `uule` parameters can't be used together. It is recommended to specify `location` at the city level in order to simulate a real user’s search. If `location` is omitted, the search may take on the location of the proxy.
uulestring
Parameter is the Google encoded location you want to use for the search. `uule` and `location` parameters can't be used together. Head to UULE Generator if you need to convert a location or GPS coordinates to `uule` parameter, and vice versa.
json_restrictorstring
Parameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details.
4. Response
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
Related APIs
| API | Price | Response |
|---|---|---|
Google EventsThis API Google | $0.01 per call | JSON |
Google | $0.01 per call | JSON |
Google | $0.015 per call | JSON |
Google | From $0.002 per call | JSON |
Google | From $0.0015 per call | JSON |
Google | $0.01 per call | JSON |
Questions
FAQ
How do I use the Google Events API?
Send a POST request to https://api.sandbase.ai/v1/api/google/events with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
How much does the Google Events API cost?
$0.01 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
What parameters does the Google Events API accept?
Required: q (string). Optional: location (string), uule (string) and json_restrictor (string). The Parameters table and the Playground on this page list every field.
What does the Google Events API return?
A JSON response returned in the same HTTP request (synchronous).
Do I need a Google developer account or API key?
No. Google Events runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Google API access separately.