ZipRecruiter: scrapers and the official API, compared

Route map

Each line is one way to get ZipRecruiter data; each stop is a field you probably need. Green lines are catalogue Actors, ranked by the published formula.

Which route for which job

The catalogue Actors for ZipRecruiter return different records. "Only this route" lists the published fields no other Actor in this table returns, which is usually what decides the choice. Cost is the published per-result rate; start events and platform usage are extra.

Field matrix: who returns what

Every tool with a published output schema, against the 6 fields most ZipRecruiter jobs need. A dot means the field name appears in the schema; rows can still leave it empty.

Field dictionary: the exact keys

The same core field has a different key in each Actor's output. Map these before you merge datasets; a dash means the published schema has no matching key. Need a field that is not listed here, such as email? Search every ZipRecruiter Actor by field.

Download this comparison: CSV · JSON (every tool with a published schema, matching keys per core field, price and score).

All 10 tools, scored

Catalogue Actors link to their detail pages; the score (0 to 100) is the published formula, identical for every tool. Other Store tools follow in their own table, for reference. Price is the published primary-result rate per 1,000 (the Free-plan rate where the price is tiered; higher Apify plans pay less); start events and platform usage are excluded.

Other Store tools, for reference

Scored with the same published formula and listed for comparison only; this site does not link or recommend them.

What to check before you choose

ZipRecruiter listings help recruiting and research teams follow hiring demand by employer, role and location. For compensation work, the useful distinction is between pay attached to a vacancy and a separate salary benchmark.

A full-description extractor suits work that needs vacancy text, subject to confirming that output in the published schema. The search-and-salary route distinguishes job and salary records and lists company attributes, while official integrations require partner approval and contract terms.

Checklist

• Confirm description and salary output before choosing by title.
• Choose an identity rule before combining runs. The full-description extractor describes listingKey as a stable listing key, while the search-and-salary tool describes id as an open seat identifier, listing key or canonical URL.
• Separate job and salary records using recordType when available. Check whether company attributes are populated on the records you intend to use for employer analysis.

Where the data is incomplete

A tool's compensation use case does not confirm that every vacancy includes usable pay information.

Listing identity also needs care: jid, listingKey and matchId describe different identifiers, and the search-and-salary tool permits several forms of id. Neither the schema nor a successful collection establishes that the results cover every relevant opening or that every listing remains active.

Official API route

Terms and personal data

Limit collection to public job listings and review ZipRecruiter's terms before storing or republishing vacancy content. Partner integrations also require compliance with their approval and contract conditions. This is general information, not legal advice.

Read ZipRecruiter's terms. Keep to public data, do not bypass logins or access controls, and check whether personal data is involved before you collect it. The can-I-scrape checklist walks through it.

How to start

1. Configure a small collection for a narrowly defined hiring market and review the documented result charges before starting it.
2. Inspect title, company, location and url, confirm whether the needed description and salary content is present, and export the records with their listing identifiers.

Call ZipRecruiter Jobs with Full Description Extractor from code

The example input uses the Actor's published defaults; set your own ZipRecruiter query before you run it. You need an Apify API token.

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run_input = {
    "startUrls": [
        "https://www.ziprecruiter.com/jobs-search?search=software+engineer&location=New+York%2C+NY"
    ],
    "searchQueries": [],
    "locations": [],
    "jobType": "any",
    "workplace": "any",
    "remoteOnly": False,
    "experienceLevels": [],
    "daysPosted": 0,
    "radiusMiles": 0,
    "salaryMin": 0,
    "salaryMax": 0,
    "quickApplyOnly": False,
    "fetchDescriptions": True,
    "maxItems": 3,
    "maxSearches": 100
}

run = client.actor("dataspryva/ziprecruiter-jobs-with-full-description-extractor").call(run_input=run_input)
if run is None:
    raise RuntimeError("The Actor run was not found.")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "<YOUR_APIFY_TOKEN>" });
const input = {
    "startUrls": [
        "https://www.ziprecruiter.com/jobs-search?search=software+engineer&location=New+York%2C+NY"
    ],
    "searchQueries": [],
    "locations": [],
    "jobType": "any",
    "workplace": "any",
    "remoteOnly": false,
    "experienceLevels": [],
    "daysPosted": 0,
    "radiusMiles": 0,
    "salaryMin": 0,
    "salaryMax": 0,
    "quickApplyOnly": false,
    "fetchDescriptions": true,
    "maxItems": 3,
    "maxSearches": 100
};

const run = await client.actor("dataspryva/ziprecruiter-jobs-with-full-description-extractor").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

curl -X POST "https://api.apify.com/v2/actors/dataspryva~ziprecruiter-jobs-with-full-description-extractor/run-sync-get-dataset-items"   -H "Authorization: Bearer $APIFY_TOKEN"   -H "Content-Type: application/json"   -d '{"startUrls":["https://www.ziprecruiter.com/jobs-search?search=software+engineer&location=New+York%2C+NY"],"searchQueries":[],"locations":[],"jobType":"any","workplace":"any","remoteOnly":false,"experienceLevels":[],"daysPosted":0,"radiusMiles":0,"salaryMin":0,"salaryMax":0,"quickApplyOnly":false,"fetchDescriptions":true,"maxItems":3,"maxSearches":100}'

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=dataspryva/ziprecruiter-jobs-with-full-description-extractor",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Questions people ask

More on ZipRecruiter

• Error fix403 Forbidden with cf-mitigated: challenge: Cloudflare blocks
• Topic groupJobs and hiring data: every website compared
• ToolWhich ZipRecruiter route fits your job?
• ToolZipRecruiter cost by Apify plan, rows and runs

Related websites

• Indeed2 Actors
• SimplyHired1 Actor

Sources

• ZipRecruiter Jobs with Full Description Extractor on Apify Store
• ZipRecruiter Job Search Results & Salary Scraper on Apify Store
• ZipRecruiter partner APIs documentation
• ZipRecruiter terms