ZipRecruiter Scraper API: Jobs, Salaries and Reviews as JSON
ZipRecruiter pages are rendered by JavaScript and protected by bot detection, so a plain HTTP fetch often returns a shell or a block page.
Scraping API takes a public ZipRecruiter URL, renders it in a real browser, rotates the IP, and returns the page content or structured JSON. You can pull job listings, salary ranges and company reviews without maintaining your own headless browser fleet or proxy pool.
What you can collect
Most ZipRecruiter scraping projects fall into three buckets: full job postings, pay bands broken out by role and location, and employer review content. A request can return title, employer, location, posting date, salary range, required skills, company rating and review text. The exact fields depend on what the public page exposes and on the extraction rules you supply.
Choose an extraction mode
There are three practical ways to get data back, and the right choice depends on how stable the page markup is and how much control you need.
- Raw HTML: send the URL and receive the rendered page. You parse it yourself. Best when you already have a parser or want to inspect the markup first.
- extract_rules with CSS or XPath selectors: you name the elements to pull and receive structured JSON. Best when the page structure is stable and you want deterministic output.
- ai_extract_rules: you describe the fields you want in plain language and the API returns structured JSON, so no selectors are needed. Best when markup changes often or you are exploring a new page type.
A useful rule of thumb: start with raw HTML to confirm the page renders, move to extract_rules once selectors are stable, and use ai_extract_rules when selector maintenance becomes the bottleneck.
Request options and what they cost
The advanced parameters are independent switches, and their credit costs stack. The table below summarizes the option behavior; check the current pricing page before committing to a volume plan.
| Option | What it does | Credit effect |
|---|---|---|
| render_js | Executes the page in a real browser | 5 credits per successful request |
| premium_proxy | Routes through premium proxies | 10 credits without JS, 25 with JS |
| stealth_proxy | Higher-trust proxy for CAPTCHA-heavy pages | 75 credits |
| country_code | Geo-targets the request | No separate credit noted |
| ai_extract_rules | Natural-language structured extraction | No separate credit noted |
| extract_rules | CSS or XPath structured extraction | No separate credit noted |
Because costs stack, a request that combines JS rendering with a premium proxy costs more than either option alone. Plan your credit budget around the combination you actually need, not the base request.
A worked example: entry-level data analyst roles
Suppose you want to compare entry-level data analyst postings across three cities. You would send one request per city search URL with render_js enabled so the job cards load. If the page returns a block page instead of listings, add stealth_proxy for that request. Once the markup is stable, add extract_rules to pull title, employer, location, posting date and salary range into JSON. If the salary field moves between page layouts, switch that field to ai_extract_rules rather than rewriting selectors. This keeps the pipeline resilient without re-rendering the page manually.
Distinguishing the three common failures
Not every empty result means the same thing, and the fix differs.
- Block page or CAPTCHA: the response contains a challenge instead of content. Scraping API handles proxy rotation to avoid IP-based blocking, and headless browser rendering mimics real user browsing behaviour to reduce blocking risk; add stealth_proxy or rotate the proxy pool.
- Shell page with no job cards: the HTML arrived before JavaScript finished. Enable render_js or wait for a selector.
- Empty fields in otherwise valid JSON: the page rendered but the selector no longer matches. Inspect the markup and update extract_rules, or move the field to ai_extract_rules.
Separating these cases early saves credits, because each fix targets a different layer of the request.
Field map for a job or company request
The following fields are the ones a request can return from public ZipRecruiter pages. Availability depends on the page type and the extraction rules you provide.
- title
- employer
- location
- posting date
- salary range
- required skills
- company rating
- review text
If a field is absent from the rendered page, it will not appear in the output regardless of extraction mode.
Getting started
Account setup begins with an API key. The signup allowance and any SDK package names are set by the service operator and should be confirmed on the current account and documentation pages before you build. You can also skip the SDK entirely and send a plain GET request with the target URL. A dashboard request builder may be offered for testing without code, but check whether it is available in your account. Published code samples cover Python, Node.js, Ruby, PHP, Go and cURL.
Before you deploy
Public-facing pages can usually be collected, but review the target site's terms of service and avoid post-login content. Data-protection obligations depend on what you collect and where you operate, so confirm the applicable GDPR, CCPA or other privacy requirements with your own legal or compliance adviser before deployment. Plan for the credit cost of the options you combine, and test on a small set of URLs before scaling.
| Option | What it does | Credit effect |
|---|---|---|
| render_js | Executes the page in a real browser | 5 credits per successful request |
| premium_proxy | Routes through premium proxies | 10 credits without JS, 25 with JS |
| stealth_proxy | Higher-trust proxy for CAPTCHA-heavy pages | 75 credits |
| country_code | Geo-targets the request | No separate credit noted |
| ai_extract_rules | Natural-language structured extraction | No separate credit noted |
| extract_rules | CSS or XPath structured extraction | No separate credit noted |
Credit costs reflect the supplied pricing material and may change; verify current pricing before committing to a plan.
Frequently asked questions
Do I need a ZipRecruiter account to use the scraper?
No. You only need an API key from Scraping API. Sign up, note the trial allowance shown at registration, send the public URL, and the rendering and proxy handling are done for you.
Is scraping ZipRecruiter allowed?
Public-facing pages are generally collectable, but you should review ZipRecruiter's terms of service before deploying and avoid content behind a login. Legal requirements vary by jurisdiction and use case.
What data can I extract from ZipRecruiter?
Anything that renders on the public page. Use extract_rules with CSS or XPath selectors for deterministic fields, or ai_extract_rules to describe the fields you want in plain language and receive structured JSON.
How do I make my first request?
Sign up, copy your API key, and send a GET request with the target ZipRecruiter URL. Scraping API renders the page, rotates the proxy, and returns the response. Check the trial allowance shown in your account to see how many test requests it covers.
Which languages and SDKs are supported?
SDK packages are offered for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works as well. Confirm the current package names in the documentation, then use whichever stack your project already relies on.
How are credits charged per request?
The base request starts at 1 credit. Enabling render_js adds 5 credits per successful request. premium_proxy costs 10 credits without JS and 25 with JS. stealth_proxy costs 75 credits. Plan prices and allowances are set by the service operator; check the current pricing page for the latest figures.