# ZipRecruiter Job Scraper (`datascrapers/ziprecruiter-scraper`) Actor

Extracts ZipRecruiter job listings — title, company, location, description, employment type, and posting dates — by search query, location, and radius. Delivers structured job records to the Apify dataset.

- **URL**: https://apify.com/datascrapers/ziprecruiter-scraper.md
- **Developed by:** [Farhan Ali](https://apify.com/datascrapers) (community)
- **Categories:** Jobs, Agents, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 jobs

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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 Job Scraper** creates a structured dataset of job listing records collected from ZipRecruiter. Each dataset item describes one job posting and can include the job title, company name, job URL, full description, employment type, posting dates, location fields, geo coordinates, company links, and the source query that produced it. Query the source using search keywords combined with optional locations and a search radius, control the result limit with `maxJobs`, and retrieve records through the Apify Dataset API or export them as JSON, CSV, Excel, XML, or another supported format.

### Dataset at a glance

| Property | Value |
|---|---|
| Source | ziprecruiter.com |
| Record unit | One job listing |
| Input methods | `searchQueries` + `locations` + `radius` (or `startUrls`) |
| Main identifiers | `url` |
| Delivery | Apify Dataset and API |
| Export formats | JSON, CSV, Excel, XML |
| Update model | Fresh records per Actor run |
| Pricing | $1 per 1,000 jobs |

### Coverage and available records

The Actor returns job listings from ZipRecruiter search results. Supported coverage includes:

- Search results built from each search keyword, optionally combined with each location.
- A search radius in miles (0 = any distance).
- Direct search URLs via `startUrls` as an override for power users.
- Title, company name, description, employment type, and posting dates.
- Structured location fields (locality, region, country, postal code) and geo coordinates.
- Company website and social links, and a direct-apply flag.

When both `searchQueries` and `startUrls` are provided, the search queries take precedence. Fields that ZipRecruiter does not provide on a listing are returned empty or null rather than guessed.

### Data dictionary

| Field | Type | Nullable | Description | Example |
|---|---:|---|---|---|
| `title` | string | No | Job posting title | `"Web Developer"` |
| `companyName` | string | Yes | Hiring company name | `"Acme GmbH"` |
| `url` | string | No | Job posting URL | `"https://www.ziprecruiter.com/job/..."` |
| `description` | string | Yes | Full job description | `"We are looking for..."` |
| `employmentType` | string | Yes | Employment type | `"FULL_TIME"` |
| `datePosted` | string | Yes | Posting date | `"2025-07-10"` |
| `validThrough` | string | Yes | Posting expiry date | `"2025-08-09"` |
| `locationLocality` | string | Yes | City | `"Berlin"` |
| `locationRegion` | string | Yes | State/region | `"Berlin"` |
| `locationCountry` | string | Yes | Country | `"DE"` |
| `locationPostalCode` | string | Yes | Postal code | `"10115"` |
| `latitude` | number | Yes | Location latitude | `52.52` |
| `longitude` | number | Yes | Location longitude | `13.405` |
| `companyUrl` | string | Yes | Company website URL | `"https://www.acme.com"` |
| `companySameAs` | string | Yes | Company social/linked URL | `"https://www.linkedin.com/company/acme"` |
| `directApply` | boolean | Yes | Whether direct application is supported | `true` |
| `sourceQuery` | string | Yes | Search query that produced the record | `"Web Developer"` |

The most stable field for deduplication is `url`.

### Example dataset record

```json
{
  "title": "Web Developer",
  "companyName": "Acme GmbH",
  "url": "https://www.ziprecruiter.de/job/abc123",
  "employmentType": "FULL_TIME",
  "datePosted": "2025-07-10",
  "validThrough": "2025-08-09",
  "locationLocality": "Berlin",
  "locationRegion": "Berlin",
  "locationCountry": "DE",
  "locationPostalCode": "10115",
  "latitude": 52.52,
  "longitude": 13.405,
  "companyUrl": "https://www.acme.com",
  "companySameAs": "https://www.linkedin.com/company/acme",
  "directApply": true,
  "description": "We are looking for a Web Developer to join our team.",
  "sourceQuery": "Web Developer"
}
```

This record was produced by a search for `Web Developer` in `Berlin` with radius `0`.

### Query and input reference

| Input | Type | Required | Default | Accepted values | Description |
|---|---:|---|---|---|---|
| `searchQueries` | array of strings | No | `[]` | Job titles, skills, or keywords | Primary input for building searches. |
| `startUrls` | array of URLs | No | `[]` | Full ZipRecruiter search URLs | Optional override; ignored when `searchQueries` is provided. |
| `locations` | array of strings | No | `[]` | City, state, or country names | Combined with each search query. |
| `radius` | integer | No | `0` | `0`–`200` miles | Search radius from the location. |
| `maxJobs` | integer | No | `0` | `0` (unlimited) or any positive integer | Maximum number of job listings; `0` means unlimited. |
| `proxyConfiguration` | object | No | Apify Residential | Apify proxy settings | Proxy configuration. |

Minimal request:

```json
{
  "searchQueries": ["Web Developer"]
}
```

Request with location and result limit:

```json
{
  "searchQueries": ["Web Developer"],
  "locations": ["Berlin"],
  "radius": 0,
  "maxJobs": 50
}
```

### Retrieve the data through the API

1. Start the Actor with a JSON input containing `searchQueries` (and optional `locations`).
2. Wait for the run to finish, or use the synchronous run endpoint.
3. Retrieve items from the run's default dataset.
4. Paginate or export the dataset.

Example in Python:

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("datascrapers/ziprecruiter-scraper").call(run_input={
    "searchQueries": ["Web Developer"],
    "locations": ["Berlin"],
    "maxJobs": 50,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["title"], item["companyName"])
```

For other languages, use the generated API tab in the Apify Console. Never place a real token in a URL or example.

### Data quality and record handling

- Fields not present on a listing are returned empty or null; completeness varies by listing.
- Location and geo coordinates are populated when ZipRecruiter provides structured location data.
- Source-side changes to ZipRecruiter's listing markup can reduce field completeness.
- The Actor does not perform internal cross-run deduplication; each run is a fresh dataset.
- The recommended external deduplication key is `url`.
- Failed requests are retried and logged; they do not abort the whole run.

### Export and pipeline examples

| Destination | Recommended method | Typical use |
|---|---|---|
| PostgreSQL/Supabase | Dataset API or webhook consumer | Job market database |
| Google Sheets | Apify integration | Manual job tracking |
| S3/cloud storage | Scheduled export or integration | Nightly job snapshot |

### Pricing and cost examples

The Actor charges per job record written to the dataset, plus a one-time Actor start event. The per-result rate is $0.001.

| Jobs | Estimated base cost |
|---:|---:|
| 1,000 | $1.00 |
| 10,000 | $10.00 |

Estimates depend on the verified pricing model and any selected proxy options. Standard Apify plan discounts may apply.

### Limitations and responsible data use

- Collects publicly accessible ZipRecruiter job listings only.
- Availability depends on source-site uptime and any listing changes.
- Some fields (employment type, dates, coordinates) are conditional and may be missing.
- No historical snapshots are stored unless you keep the datasets yourself.
- You are responsible for complying with ZipRecruiter's terms and applicable law when using the data.

### Dataset questions

#### What does one dataset item represent?

One ZipRecruiter job listing, including title, company, description, location, employment type, and posting dates.

#### Which field should I use as a unique identifier?

`url` is the stable job posting URL and is the recommended deduplication key.

#### Are fields nullable or conditional?

Yes. `employmentType`, `datePosted`, `validThrough`, location fields, and coordinates depend on the individual listing.

#### Can I retrieve the records as CSV or JSON?

Yes. The dataset can be exported as JSON, CSV, Excel, or XML from the Apify Console or Dataset API.

#### How do I paginate large datasets?

Use the Dataset API pagination, or raise `maxJobs` (set `0` for all results) to collect more records in a single run.

#### Does the Actor return historical data?

No. Each run returns listings visible at run time.

#### What counts as a billable result?

Each job record written to the dataset is one billable result, at $0.001 per job.

### Related datasets from Data Scrapers

- [StepStone Jobs Scraper](https://apify.com/datascrapers/stepstone-jobs-scraper) — European job postings for cross-board market coverage.
- [Glassdoor Jobs Scraper](https://apify.com/datascrapers/glassdoor-jobs-scraper) — job records with employer ratings that can be joined to listings.
- [LinkedIn Company Scraper](https://apify.com/datascrapers/linkedin-company-scraper) — company profile records for employer enrichment.
- [LinkedIn Profile Scraper](https://apify.com/datascrapers/linkedin-profile-scraper) — professional profile records for the same talent-market use cases.

### Data Scrapers support

Need an additional field, record type, or export workflow? Contact Data Scrapers at stardustspotlight@gmail.com. Include a sample source URL, required fields, expected record volume, and preferred delivery format.

# Actor input Schema

## `searchQueries` (type: `array`):

Job titles, skills, or keywords (e.g. "Python Developer", "Data Scientist", "Registered Nurse Brooklyn"). Primary input for AI agents — no URL required. Combine with Locations below for location-specific searches.

## `startUrls` (type: `array`):

Full ZipRecruiter search URLs copied from your browser (e.g. https://www.ziprecruiter.de/jobs/search?q=python\&l=Berlin). Optional override for power users — ignored when Search Queries are provided.

## `locations` (type: `array`):

City, state, or country names (e.g. "Berlin", "New York, NY", "Remote"). Leave empty for nationwide or remote search. Combined with each Search Query.

## `radius` (type: `integer`):

Search radius in miles from the location (0 = any distance). Applies to all location searches.

## `maxJobs` (type: `integer`):

Maximum number of job listings to scrape (0 = unlimited). Use a specific number to control costs and runtime.

## `proxyConfiguration` (type: `object`):

Proxy settings for anti-bot protection. Apify Residential proxy recommended for reliable scraping.

## Actor input object example

```json
{
  "searchQueries": [
    "Web Developer"
  ],
  "startUrls": [
    {
      "url": "https://www.ziprecruiter.de/jobs/search?q=Web+Developer&l=Berlin"
    }
  ],
  "locations": [
    "Berlin"
  ],
  "radius": 0,
  "maxJobs": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `dataset` (type: `string`):

JSON array of scraped job records. Fetch this URL after the run completes to retrieve results.

## `run` (type: `string`):

Apify Console link to inspect this run's logs, input, and output.

# 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 = {
    "searchQueries": [
        "Web Developer"
    ],
    "startUrls": [
        {
            "url": "https://www.ziprecruiter.de/jobs/search?q=Web+Developer&l=Berlin"
        }
    ],
    "locations": [
        "Berlin"
    ],
    "maxJobs": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("datascrapers/ziprecruiter-scraper").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 = {
    "searchQueries": ["Web Developer"],
    "startUrls": [{ "url": "https://www.ziprecruiter.de/jobs/search?q=Web+Developer&l=Berlin" }],
    "locations": ["Berlin"],
    "maxJobs": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("datascrapers/ziprecruiter-scraper").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 '{
  "searchQueries": [
    "Web Developer"
  ],
  "startUrls": [
    {
      "url": "https://www.ziprecruiter.de/jobs/search?q=Web+Developer&l=Berlin"
    }
  ],
  "locations": [
    "Berlin"
  ],
  "maxJobs": 20
}' |
apify call datascrapers/ziprecruiter-scraper --silent --output-dataset

```

## MCP server setup

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

```

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/65jCEbXjqqgW3v1KL/builds/lgT4ZtKCbWLO1j0op/openapi.json