/ziprecruiter/jobs/search

POST /api/ziprecruiter/jobs/search

Price: 20 credits

Search ZipRecruiter jobs by keyword and location

How to use it

Search ZipRecruiter job listings by keyword, optionally narrowed to a 'City, ST' location. Each result carries the job id, title, hiring company (name, alias, logo), location, salary, employment and location types, benefits, a short snippet, the posting date, and the job URL.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• search string required — Search keyword or job title (minLength: 1)
• count integer required — Max number of jobs to return (min: 1)
• location string nullable — Location as 'City, ST' (two-letter state), e.g. 'Austin, TX'

Response

• @type string (default: "ZiprecruiterJob")
• id string required
• listing_key string nullable
• company object nullable
  • @type string (default: "ZiprecruiterJobCompany")
  • name string nullable
  • alias string nullable
  • image string nullable
  • company_url string nullable
• location object nullable
  • @type string (default: "ZiprecruiterJobLocation")
  • display string nullable
  • city string nullable
  • state string nullable
  • state_code string nullable
  • county string nullable
  • country string nullable
  • country_code string nullable
  • postal_code string nullable
• salary object nullable
  • @type string (default: "ZiprecruiterJobSalary")
  • salary_min number nullable
  • salary_max number nullable
  • period string nullable
  • currency string nullable
  • display string nullable
• employment_types array (default: [])
• location_types array (default: [])
• benefits array (default: [])
• snippet string nullable
• posted_at string nullable
• is_active boolean nullable
• job_url string nullable
• apply_url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.