# ZipRecruiter Jobs Scraper (`usestring/ziprecruiter-jobs`) Actor

Collect ZipRecruiter job listings - salary, company, location.

- **URL**: https://apify.com/usestring/ziprecruiter-jobs.md
- **Developed by:** [String](https://apify.com/usestring) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## ZipRecruiter Jobs Scraper — advertised salary, company, location

The ZipRecruiter Jobs Scraper collects job listings from ZipRecruiter search results. Give it search
terms and a location, and it returns each listing with the **advertised** pay as numbers, the pay
interval and currency, the employment type, a split city and state, ZipRecruiter's own posted
timestamp and the apply URL.

To scrape ZipRecruiter jobs, put one or more job titles or keywords in `queries` and a `location`
such as `"Austin, TX"` or a ZIP code. No ZipRecruiter account, login or cookies are used; this Actor
reads what a logged-out visitor sees. Around **20 jobs per search**.

### What it returns

| Field | Type | Notes |
| --- | --- | --- |
| `jobId` | string | ZipRecruiter's own listing key — stable, use it to de-duplicate |
| `title` | string | |
| `company` | string | |
| `salaryMin`, `salaryMax` | number | The **advertised** pay, e.g. `85000` and `110000`. `null` when the posting advertises none — see below |
| `salaryPeriod` | string | The interval the pay is quoted over, e.g. `"year"`, `"hour"` |
| `currency` | string | ISO code, e.g. `"USD"` |
| `employmentType` | string | e.g. `"full_time"` |
| `location` | string | As ZipRecruiter displays it, e.g. `"Melbourne, FL US"` |
| `city`, `state` | string | Split out, so you can group without parsing |
| `postedAt` | string | ISO 8601 timestamp from ZipRecruiter's own posted date — a real timestamp, not a day count |
| `jobUrl` | string | Direct link to the ZipRecruiter posting |
| `query`, `sourceUrl`, `collectedAt` | string | Provenance for every row |

### Input

```json
{ "queries": ["software engineer", "registered nurse"], "location": "Austin, TX" }
```

| Field | Description |
| --- | --- |
| `queries` | Job titles or keywords. Required, 1–50. Duplicates collapse to one fetch. |
| `location` | City, state or ZIP. Default `"United States"`. One location per run. |
| `maxItems` | Cap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below. |
| `concurrency` | Searches run in parallel. Default 3. |

### Use cases

- Compensation benchmarking on advertised pay only, with no estimates mixed in
- Talent-market research by role, city and state
- Filling an ATS or job board with live ZipRecruiter postings
- Recruiting lead lists by role, employer or metro
- Tracking ZipRecruiter postings over time by re-running on a schedule, joined on `jobId`

### Reliability

The ZipRecruiter Jobs Scraper reads the search page's own data payload rather than the schema.org
markup beside it. That markup is an `ItemList` carrying a title and a link per job; the payload
carries pay as numbers with an explicit interval and currency, the employer's posted date, a resolved
city and state, and the employment type.

**Only advertised pay is returned.** ZipRecruiter also computes its own salary estimate for postings
that quote none, and marks it as not for display. This Actor drops that block rather than passing an
estimate off as the advertised range, so `salaryMin` is `null` exactly when the employer named no
figure. A flat rate — `"$57 an hour"` — returns `salaryMin: 57` and `salaryMax: null`, because one
figure is a rate and not a range.

A ZipRecruiter search that cannot be read is recorded in the run's `SUMMARY` under `failures`, and a
run where every search failed exits with an error.

### Frequently asked questions

**Do I need a ZipRecruiter account, login or API key?** No. The ZipRecruiter Jobs Scraper uses no
account, login, cookies or API key — only public ZipRecruiter search pages are read.

**Is the ZipRecruiter salary advertised or estimated?** Advertised. ZipRecruiter's own estimate for
postings that quote no pay is deliberately discarded, so `salaryMin` and `salaryMax` are `null`
rather than filled with a guess.

**Is the salary a number?** Yes — `salaryMin` and `salaryMax` are numbers, with `salaryPeriod`
(`"year"`, `"hour"`) and `currency` (`"USD"`) alongside, so hourly and annual pay are never confused.

**How many ZipRecruiter jobs does one search return?** Around 20, which is what one ZipRecruiter
results page carries. Ten search terms therefore return roughly 200 jobs.

**Can I get the full ZipRecruiter job description?** No. This Actor returns the fields ZipRecruiter
exposes on the search results page; it does not open each posting. Follow `jobUrl` for the full
description.

**Can I search several locations in one run?** No — one run searches one `location` across all of
its `queries`. Start one run per location.

**What happens on a free Apify plan?** The run stops at 250 requests and 250 results and reports
that it hit the limit. Any paid plan runs the full input.

### Limitations

The ZipRecruiter Jobs Scraper reads one results page per search, so it collects the first page rather
than paginating a whole market; run several narrower queries to widen coverage. Full job
descriptions, company profiles, applicant counts and recruiter contacts are out of scope, as is
searching more than one location per run.

### Free plan limit

Runs started from an Apify **free plan** stop at **250 requests and 250 results**, and the run
reports that it reached the limit. Any paid plan runs the full input and `maxItems` you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not
cover for free-plan runs. It binds on requests as well as results so that a large input list cannot
spend those fetches for rows the run will not return.

# Actor input Schema

## `queries` (type: `array`):

Job titles or keywords.

## `location` (type: `string`):

City, state or ZIP.

## `maxItems` (type: `integer`):

Global cap on dataset items. Runs started from an Apify free plan stop at 250 requests and 250 results; any paid plan runs the full amount.

## `concurrency` (type: `integer`):

Targets fetched in parallel.

## Actor input object example

```json
{
  "queries": [
    "software engineer"
  ],
  "location": "United States",
  "maxItems": 1000,
  "concurrency": 3
}
```

# Actor output Schema

## `results` (type: `string`):

Collect ZipRecruiter job listings - salary, company, location.

## `summary` (type: `string`):

Item count, failure count and every target that failed, with its error.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "queries": [
        "software engineer"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("usestring/ziprecruiter-jobs").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "queries": ["software engineer"] }

# Run the Actor and wait for it to finish
run = client.actor("usestring/ziprecruiter-jobs").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "queries": [
    "software engineer"
  ]
}' |
apify call usestring/ziprecruiter-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,usestring/ziprecruiter-jobs"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/EVq88UlRHRPXnZOf3/builds/bXusE5l5PzViOZ8EM/openapi.json