# ZipRecruiter Job Scraper (`moving_beacon-owner1/ziprecruiter-job-scraper`) Actor

Scrapes ZipRecruiter job listings by keyword and location, returning job title, company, location, work setting, salary, job URL, company URL, badges, and description snippets.

- **URL**: https://apify.com/moving\_beacon-owner1/ziprecruiter-job-scraper.md
- **Developed by:** [Jamshaid Arif](https://apify.com/moving_beacon-owner1) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 33.3% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $9.99 / 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.

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

Scrapes job listings from [ZipRecruiter](https://www.ziprecruiter.com) by keyword
and location.

### Input

| Field | Default | Description |
| --- | --- | --- |
| `query` | `software engineer` | Job title or keyword; converted to a browse slug (`/Jobs/Software-Engineer`). |
| `location` | `""` | `"City, ST"`, e.g. `"Austin, TX"`. Empty = nationwide. |
| `nationwide_fallback` | `true` | If the location has no browse page, scrape the nationwide feed and filter on the location text. |
| `max_results` | `20` | Maximum records to return (1–500). 20 jobs per page, up to 25 pages. |

The actor runs with empty input, defaulting to "software engineer" nationwide.

### Output

One record per job listing:

```json
{
  "job_id": "dCMqP5rQB7ezN_pB4MHD_w",
  "title": "Senior Software Engineer",
  "company": "WeInfuse",
  "location": "Austin, TX",
  "work_setting": "On-site",
  "salary": "$135K - $170K/yr",
  "salary_min": 135000.0,
  "salary_max": 170000.0,
  "badges": ["Quick apply"],
  "snippet": "We're not rockstars or ninjas, just a team of developers…",
  "job_url": "https://www.ziprecruiter.com/c/WeInfuse/Job/Senior-Software-Engineer/-in-Austin,TX?jid=0cb24f3b993a8e24",
  "company_url": "https://www.ziprecruiter.com/co/WeInfuse/Jobs/-in-Austin,TX",
  "search_query": "software engineer",
  "search_location": "Austin, TX",
  "raw": { "…": "the parsed card fields, unnormalised" }
}
```

`salary_min` / `salary_max` are parsed from the pay line (`$135K - $170K/yr` →
`135000` / `170000`); both are `null` when the employer published no salary.

### Data source and auth

Public browse pages at `https://www.ziprecruiter.com/Jobs/…`. No API key, no
account. ZipRecruiter only publishes browse pages for **city + state** pairs — a
state on its own (`"Texas"`) or a city alone returns 404, so those requests use the
nationwide feed filtered client-side. Some title/city combinations return `410` and
likewise fall back. Employment type is not exposed on browse cards; `badges` holds
whatever benefit and apply markers the card shows.

### Caveats

ZipRecruiter runs Cloudflare bot management. The actor retries across several TLS
impersonation profiles and paces requests (~0.9 s between pages), which is enough
for the browse pages from ordinary IPs, but sustained or high-volume runs may still
be challenged — residential proxies help. Respect ZipRecruiter's Terms of Service
and robots policy, and keep request volumes modest.

# Actor input Schema

## `query` (type: `string`):

Job title or keyword to search for, e.g. "software engineer", "registered nurse", "truck driver". It is converted into a ZipRecruiter browse slug such as /Jobs/Software-Engineer.

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

Location as "City, ST", e.g. "Austin, TX". ZipRecruiter only publishes browse pages for city+state pairs; a state alone ("Texas") or an unknown pair falls back to the nationwide feed filtered on this text. Leave empty for nationwide.

## `nationwide_fallback` (type: `boolean`):

When the requested location has no dedicated ZipRecruiter browse page, scrape the nationwide feed and filter it on the location text instead. Turn this off to return no records rather than approximate ones.

## `max_results` (type: `integer`):

Maximum number of job records to return. ZipRecruiter serves 20 jobs per browse page; the actor walks numbered pages until this many are collected (up to 25 pages).

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

Proxy settings for the run. Enable a US-based proxy for the most reliable results, especially for sites that limit non-US or datacenter traffic. Optional — leave off to run directly.

## Actor input object example

```json
{
  "query": "software engineer",
  "location": "Austin, TX",
  "nationwide_fallback": true,
  "max_results": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyCountry": "US"
  }
}
```

# Actor output Schema

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

No description

# 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 = {
    "query": "software engineer",
    "location": "Austin, TX",
    "nationwide_fallback": true,
    "max_results": 20,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyCountry": "US"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("moving_beacon-owner1/ziprecruiter-job-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 = {
    "query": "software engineer",
    "location": "Austin, TX",
    "nationwide_fallback": True,
    "max_results": 20,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyCountry": "US",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("moving_beacon-owner1/ziprecruiter-job-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 '{
  "query": "software engineer",
  "location": "Austin, TX",
  "nationwide_fallback": true,
  "max_results": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyCountry": "US"
  }
}' |
apify call moving_beacon-owner1/ziprecruiter-job-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,moving_beacon-owner1/ziprecruiter-job-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/qz8lcca6UeUOeKCHe/builds/CPJRMUqrXhPR7bqlC/openapi.json