qstringrequired
Parameter defines the query you want to search.
https://api.sandbase.ai/v1/api/google/jobsSearch job listings aggregated by Google Jobs with title, company, location, posting date, salary and apply links, filtered by location and language.
Your output will appear here
Complete the inputs, then click Run.
Search job listings aggregated by Google Jobs with title, company, location, posting date, salary and apply links, filtered by location and language.
curl -X POST "https://api.sandbase.ai/v1/api/google/jobs" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"q": "data engineer", "location": "Austin, Texas, United States"}'
The result is returned in outputs[0].data as structured JSON.
| Name | Type | Required | Description |
|---|---|---|---|
q | string | Yes | Parameter defines the query you want to 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 page for a full list of supported Google domains. |
gl | string | No | Parameter defines the country to use for the Google Jobs 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 Jobs countries page for a full list of suppo |
hl | string | No | Parameter defines the language to use for the Google Jobs 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. |
next_page_token | string | No | Parameter defines the next page token. It is used for retrieving the next page of results. Up to 10 results are returned per page. The next page token can be found in the the API JSON response: the API_pagination -> next_page_token Usag |
chips | string | No | Parameter defines additional query conditions. Top of a job search page contains elements called chips, its values are extracted in order to be passed to chips parameter. E.g. city:Owg_06VPwoli_nfhBo8LyA== will return results for New York |
lrad | string | No | Defines search radius in kilometers. Does not strictly limit the radius. |
ltype | string | No | Parameter will filter the results by work from home. This parameter has been deprecated by Google. |
uds | string | No | Parameter enables to filter search. It's a string provided by Google as a filter. uds values are provided under the section: filters with uds, q and the API_link values provided for each filter. |
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. |
$0.010 per successful call. Failed calls are not charged.
Start building
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/jobs" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"q": "data engineer",
"location": "Austin, Texas, United States"
}
SANDBASE_JSON
)
printf '%s\n' "$result"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.
qstringrequiredParameter defines the query you want to search.
locationstringParameter 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.
uulestringParameter 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_domainstringParameter defines the Google domain to use. It defaults to `google.com`. Head to the Google domains page for a full list of supported Google domains.
glstringParameter defines the country to use for the Google Jobs 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 Jobs countries page for a full list of supported Google Jobs countries. When `location` is set, it defaults to the country of the location, if Google Jobs supports that country.
hlstringParameter defines the language to use for the Google Jobs 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. Searches fall back to English (`en`) when Google has no Google Jobs page in the requested or default language, such as Polish or Romanian. Send `hl=en` to skip the extra tries.
next_page_tokenstringParameter defines the next page token. It is used for retrieving the next page of results. Up to `10` results are returned per page. The next page token can be found in the the API JSON response: `the API_pagination -> next_page_token` Usage of `start` parameter (results offset) has been discontinued by Google.
chipsstringParameter defines additional query conditions. Top of a job search page contains elements called chips, its values are extracted in order to be passed to chips parameter. E.g. `city:Owg_06VPwoli_nfhBo8LyA==` will return results for New York. This parameter has been deprecated by Google.
lradstringDefines search radius in kilometers. Does not strictly limit the radius.
ltypestringParameter will filter the results by work from home. This parameter has been deprecated by Google.
udsstringParameter enables to filter search. It's a string provided by Google as a filter. `uds` values are provided under the section: `filters` with `uds`, `q` and `the API_link` values provided for each filter.
json_restrictorstringParameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details.
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
| API | Price | Response |
|---|---|---|
Google JobsThis 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
Send a POST request to https://api.sandbase.ai/v1/api/google/jobs 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.
$0.01 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: q (string). Optional: location (string), uule (string), google_domain (string), gl (string), hl (string) and next_page_token (string) and 5 more. The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. Google Jobs 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.