qstringrequired
Parameter defines the query you want to search. You can use anything that you would use in a regular Google Local search.
Google Local
https://api.sandbase.ai/v1/api/google/localSearch local businesses on Google by keyword and location, with name, rating, reviews, address, hours, phone and place ID.
- Price
- $0.01USD / call
- Method
- POST
- Response
- JSON
- Parameters
- 1 required · 10 optional
Playground
Input
Parameter defines the query you want to search. You can use anything that you would use in a regular Google Local search.
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. For consistent results with coordinates-based `uule` parameter, a matching `gl` parameter is required. Head to UULE Generator if you need to convert a location or GPS coordinates to `uule` parameter, and vice versa. The radius of a coordinates-based `uule` is not used.
Parameter defines the Google domain to use. It defaults to `google.com`. Head to the Google domains for a full list of supported Google domains.
Parameter defines the country to use for the Google Local search. It's a two-letter country code. (e.g., `us` for the United States, `uk` for United Kingdom, or `fr` for France) Head to the Google countries for a full list of supported Google countries.
Parameter defines the language to use for the Google Local search. It's a two or three-letter language code. (e.g., `en` for English, `es` for Spanish, or `fr` for French), optionally followed by a two-letter or three-digit region code (e.g., `en-gb` for British English, or `es-419` for Latin American Spanish). Head to the Google languages page for a full list of supported Google languages.
Parameter defines the Google CID (customer identifier) of a place. This parameter can be found in Google Local API and Google Search API local results under the name of `place_id`, as well as in Google Maps API local results under the name of `data_cid`. You can also acquire it using Google's CID converter. Example CID for "New York, NY, USA": `14414772292044717666`.
(to be searched) parameter defines advanced search parameters that aren't possible in the regular query field.
Parameter defines the result offset. It skips the given number of results. It's used for pagination. The value depends on the number of results returned which can either be `10` or `20`. For eg, on mobile `10` results are returned, so `start` should be `10`, `20`, `30`. It's advised to use `the API_pagination.next` where we handle this automatically.
Parameter defines the device to use to get the results. It can be set to `desktop` (default) to use a regular browser, `tablet` to use a tablet browser (currently using iPads), or `mobile` to use a mobile browser.
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 Local
Search local businesses on Google by keyword and location, with name, rating, reviews, address, hours, phone and place ID.
Request
curl -X POST "https://api.sandbase.ai/v1/api/google/local" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"q": "coffee", "location": "Austin, Texas, United States"}'
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. You can use anything that you would use in a regular Google Local search. |
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. For consistent results with coordinates-based uule parameter, a matching gl parameter is required. Head to |
google_domain | string | No | Parameter defines the Google domain to use. It defaults to google.com. Head to the Google domains for a full list of supported Google domains. |
gl | string | No | Parameter defines the country to use for the Google Local search. It's a two-letter country code. (e.g., us for the United States, uk for United Kingdom, or fr for France) Head to the Google countries for a full list of supported Goog |
hl | string | No | Parameter defines the language to use for the Google Local search. It's a two or three-letter language code. (e.g., en for English, es for Spanish, or fr for French), optionally followed by a two-letter or three-digit region code (e.g |
ludocid | string | No | Parameter defines the Google CID (customer identifier) of a place. This parameter can be found in Google Local API and Google Search API local results under the name of place_id, as well as in Google Maps API local results under the name |
tbs | string | No | (to be searched) parameter defines advanced search parameters that aren't possible in the regular query field. |
start | string | No | Parameter defines the result offset. It skips the given number of results. It's used for pagination. The value depends on the number of results returned which can either be 10 or 20. For eg, on mobile 10 results are returned, so `star |
device | string | No | Parameter defines the device to use to get the results. It can be set to desktop (default) to use a regular browser, tablet to use a tablet browser (currently using iPads), or mobile to use a mobile browser. |
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/local" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"q": "coffee",
"location": "Austin, Texas, United States"
}
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. For consistent results with coordinates-based `uule` parameter, a matching `gl` parameter is required. Head to UULE Generator if you need to convert a location or GPS coordinates to `uule` parameter, and vice versa. The radius of a coordinates-based `uule` is not used.
google_domainstring
Parameter defines the Google domain to use. It defaults to `google.com`. Head to the Google domains for a full list of supported Google domains.
glstring
Parameter defines the country to use for the Google Local search. It's a two-letter country code. (e.g., `us` for the United States, `uk` for United Kingdom, or `fr` for France) Head to the Google countries for a full list of supported Google countries.
hlstring
Parameter defines the language to use for the Google Local search. It's a two or three-letter language code. (e.g., `en` for English, `es` for Spanish, or `fr` for French), optionally followed by a two-letter or three-digit region code (e.g., `en-gb` for British English, or `es-419` for Latin American Spanish). Head to the Google languages page for a full list of supported Google languages.
ludocidstring
Parameter defines the Google CID (customer identifier) of a place. This parameter can be found in Google Local API and Google Search API local results under the name of `place_id`, as well as in Google Maps API local results under the name of `data_cid`. You can also acquire it using Google's CID converter. Example CID for "New York, NY, USA": `14414772292044717666`.
tbsstring
(to be searched) parameter defines advanced search parameters that aren't possible in the regular query field.
startstring
Parameter defines the result offset. It skips the given number of results. It's used for pagination. The value depends on the number of results returned which can either be `10` or `20`. For eg, on mobile `10` results are returned, so `start` should be `10`, `20`, `30`. It's advised to use `the API_pagination.next` where we handle this automatically.
devicestring
Parameter defines the device to use to get the results. It can be set to `desktop` (default) to use a regular browser, `tablet` to use a tablet browser (currently using iPads), or `mobile` to use a mobile browser.
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 LocalThis 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 Local API?
Send a POST request to https://api.sandbase.ai/v1/api/google/local 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 Local 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 Local API accept?
Required: q (string). Optional: location (string), uule (string), google_domain (string), gl (string), hl (string) and ludocid (string) and 4 more. The Parameters table and the Playground on this page list every field.
What does the Google Local API return?
A JSON response returned in the same HTTP request (synchronous).
Do I need a Google developer account or API key?
No. Google Local 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.