# Search jobs

Returns Glassdoor job listings for `query` in one location, about 62 rows per search. Requires `loc_id`, Glassdoor's own location id — no location-name lookup is offered. No paging parameter; vary `query` and `loc_id` for more rows. `data` is null when the location id is invalid.

- Platform: Glassdoor
- Request: `GET https://api.toolzerhub.com/v1/glassdoor/jobs`
- Auth: `x-api-key` header
- Cost: 1 credit per successful request. Failed requests are not billed.
- Page: https://docs.toolzerhub.com/reference/glassdoor/jobs/search-glassdoor-jobs

| Parameter | In | Required | Type | Description |
| --- | --- | --- | --- | --- |
| `query` | query | yes | string | What to search for, as free text — Glassdoor's own sc.keyword. |
| `loc_id` | query | yes | integer | Glassdoor location ID from the locId query parameter in a glassdoor.com search URL. |
| `loc_type` | query | no | string | What kind of place loc_id names — Glassdoor's locT. C city, S state, N nation, M metro. Must match the id: a city id sent with S does not search that city's state, it searches nothing useful. Default: C. |

## Example request

```bash
curl "https://api.toolzerhub.com/v1/glassdoor/jobs?query=<query>&loc_id=<loc_id>" \
  -H "x-api-key: $TOOLZERHUB_API_KEY"
```

Success responses are wrapped as `{ "data": ... }`. Errors return `{ "error": { "code", "status", "message", "retryable", "details" } }`. See https://docs.toolzerhub.com/docs/responses-and-errors.