ZipRecruiter Job Search Results & Salary Scraper

What it returns

76 fields from the published dataset schema. Export as JSON, CSV or Excel, or read the dataset through the Apify API.

• typejob_ziprecruiter or salary_ziprecruiter
• recordTypejob or salary
• idJob identity: open seat id, listing key or canonical URL
• jidZipRecruiter job id from the jid parameter
• listingKeyZipRecruiter listing key
• openSeatIdZipRecruiter open seat id
• matchIdZipRecruiter match id
• urlCanonical job page URL
• titleJob title
• companyHiring company name
• companyIdZipRecruiter company id
• companyUrlCompany profile URL
• companyLogoCompany logo image URL
• companyWebsiteCompany website URL
• companyIndustriesCompany industries
• companySizeCompany size label
• companyHqLocationCompany headquarters
• companyRatingBreakroom company rating
• companyAboutCompany description
• companyFoundedYearCompany founding year when shown
• locationDisplay location
• cityCity
• stateState or region code
• countryCountry name
• countryCodeISO country code
• postalCodePostal code
• countyCounty
• locationIdZipRecruiter location id
• workplaceTypesonsite, remote or hybrid
• isRemoteTrue when the job is remote

How it differs from the other ZipRecruiter Actors

Among the 2 catalogue Actors for ZipRecruiter with a published schema, only this one returns isNew, skills, occupationalCategory.

Input

Example input

Built from the input form's published example values and defaults.

{
  "mode": "search",
  "searchQueries": [
    "registered nurse"
  ],
  "locations": [
    "Chicago, IL"
  ],
  "startUrls": [],
  "jobType": "any",
  "workplace": "any",
  "experienceLevels": [],
  "daysPosted": 0,
  "radiusMiles": 0,
  "salaryMin": 0,
  "salaryMax": 0,
  "fetchDescriptions": false,
  "includeCompanyProfile": false,
  "maxItems": 3,
  "maxSearches": 1,
  "salaryRoles": [
    "registered nurse"
  ],
  "salaryLocations": [
    "Chicago, IL"
  ],
  "salaryUrls": []
}

Run it from code or an AI agent

The same run through the Apify API, with the example input. You need an Apify API token; the run is billed to your account at the Store price.

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run_input = {
    "mode": "search",
    "searchQueries": [
        "registered nurse"
    ],
    "locations": [
        "Chicago, IL"
    ],
    "startUrls": [],
    "jobType": "any",
    "workplace": "any",
    "experienceLevels": [],
    "daysPosted": 0,
    "radiusMiles": 0,
    "salaryMin": 0,
    "salaryMax": 0,
    "fetchDescriptions": False,
    "includeCompanyProfile": False,
    "maxItems": 3,
    "maxSearches": 1,
    "salaryRoles": [
        "registered nurse"
    ],
    "salaryLocations": [
        "Chicago, IL"
    ],
    "salaryUrls": []
}

run = client.actor("vexaloom-labs/ziprecruiter-job-search-results-and-salary-scraper").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 = {
    "mode": "search",
    "searchQueries": [
        "registered nurse"
    ],
    "locations": [
        "Chicago, IL"
    ],
    "startUrls": [],
    "jobType": "any",
    "workplace": "any",
    "experienceLevels": [],
    "daysPosted": 0,
    "radiusMiles": 0,
    "salaryMin": 0,
    "salaryMax": 0,
    "fetchDescriptions": false,
    "includeCompanyProfile": false,
    "maxItems": 3,
    "maxSearches": 1,
    "salaryRoles": [
        "registered nurse"
    ],
    "salaryLocations": [
        "Chicago, IL"
    ],
    "salaryUrls": []
};

const run = await client.actor("vexaloom-labs/ziprecruiter-job-search-results-and-salary-scraper").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

curl -X POST "https://api.apify.com/v2/actors/vexaloom-labs~ziprecruiter-job-search-results-and-salary-scraper/run-sync-get-dataset-items"   -H "Authorization: Bearer $APIFY_TOKEN"   -H "Content-Type: application/json"   -d '{"mode":"search","searchQueries":["registered nurse"],"locations":["Chicago, IL"],"startUrls":[],"jobType":"any","workplace":"any","experienceLevels":[],"daysPosted":0,"radiusMiles":0,"salaryMin":0,"salaryMax":0,"fetchDescriptions":false,"includeCompanyProfile":false,"maxItems":3,"maxSearches":1,"salaryRoles":["registered nurse"],"salaryLocations":["Chicago, IL"],"salaryUrls":[]}'

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=vexaloom-labs/ziprecruiter-job-search-results-and-salary-scraper",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

What a run costs

The result rate falls on higher Apify plans. Each figure is the published per-result rate times the number of results.

• Every run also has a start event, charged per GB of memory (minimum one): $0.10 on Free, $0.03 on Business. At its default memory of 4 GB a run starts at $0.40 on Free. Fewer, larger runs keep this small.
• The Free plan includes $5 of monthly usage (Apify pricing, checked 2026-11-11); at the Free rate that covers at most about 5,050 results, less start events and platform usage.
• Worked example: 10,000 results in one run on the Free plan cost $10.30 ($9.90 for results + $0.40 start), plus Apify platform usage (compute), billed separately by Apify.
• Pay per event. Platform usage (compute) is billed by Apify on top of the event prices. Compare other tools in the cost estimator.

Where it fits among ZipRecruiter routes

It ranks 2 of 2 catalogue Actors for ZipRecruiter on the published formula (fields, price, reliability, freshness). Its line is highlighted on the map.

What people use it for

• Find job postings
• Analyze salary benchmarks
• Collect company profiles

Other catalogue Actors for ZipRecruiter

Similar Actors

Questions people ask

Sources

• ZipRecruiter Job Search Results & Salary Scraper on Apify Store
• Published build with input and output schema (JSON)
• ZipRecruiter partner APIs documentation