Datapika / Jobs & hiring

Hiring Signals Scanner

Company hiring activity and recent job postings. Company hiring signals and job-related records from supported sources.

5 lifetime users189 total runsNo public reviews yet

Apify store response · 2026-10-14. Usage counts do not measure output accuracy.

01 / Recorded output

See what comes back.

· Build 0.1.25 · 20 rows reviewed. Previewing 5 below.

Swipe the table to inspect more fields →

Selected fields from a recorded indeed-ziprecruiter-scraper run
record_typecompany_querytitlelocationhas_active_postings
companyInsperityNot returnedNot returnedtrue
jobInsperitySenior Insurance Accounting SpecialistThe Woodlands, TXNot returned
jobInsperitySenior Human Resource SpecialistFlorham Park, NJNot returned
jobInsperityBilingual Orientation Representative (English/Spanish)Charlotte, NCNot returned
jobInsperityAdministrator, Health & Welfare ServicesKingwood, TX, USNot returned

Selected public fields from one recorded run. Text may be shortened to 20 words and non-HTTPS links are omitted. Missing values are preserved; this sample does not establish complete source coverage. Downloads contain all reviewed rows and selected fields. CSV text cells are escaped for spreadsheet safety.

Inspect the first JSON record
{
  "record_type": "company",
  "company_query": "Insperity",
  "has_active_postings": true,
  "active_jobs_found": 36,
  "posted_last_48h_count": 16,
  "sites_checked": [
    "indeed",
    "zip_recruiter"
  ]
}

02 / Run your own query

From a console, code or agent.

Use Apify's input form, or start a run with your own API token. The small starter input below was checked against build 0.1.25's published input schema on September 9, 2026. Recorded samples can use different inputs or older builds.

curl -X POST \
  "https://api.apify.com/v2/acts/openclawai~indeed-ziprecruiter-scraper/runs?maxTotalChargeUsd=1" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"scanMode":"companies","companies":["Paychex | paychex.com"],"location":"United States","maxJobsPerCompany":5,"sites":["indeed","zip_recruiter"],"emitJobRecords":true}'

This starts an asynchronous paid run with a $1 total run cap. Use the returned defaultDatasetId to retrieve results after the run succeeds. Never put your API token in public frontend code.

Full input schema ↗·API setup and dataset export

03 / Field reference

Plan your data model.

Selected documented fields from build 0.1.25, reviewed September 9, 2026. Availability varies by mode and source. Missing and null values stay visible in the recorded samples.

Selected documented output fields
FieldTypeMeaning
record_typestringcompany = one row per target company (signal + profile). job = one flat row per job posting. keyword = per-keyword summary.
company_querystringThe company name from your input this record belongs to
titlestringJob title as shown on the posting
locationstringJob location as shown on the posting (city, state, country)
has_active_postingsbooleanWhether the company currently has active postings on either board
active_jobs_foundintegerEmployer-verified postings returned this run (bounded by maxJobsPerCompany)
posted_last_48h_countintegerMatched postings inside the hoursOld window
job_urlstringLink to the posting (direct employer link when available)
Download the dated input and field references ↓

04 / Know before you run

Coverage, without the guesswork.

Job postings indicate advertised hiring activity, not confirmed hires, headcount growth or purchase intent.

How can I check if a company is actively hiring on Indeed or ZipRecruiter?

Feed company names into the scraper and each record returns a has_active_postings flag, employer-verified posting counts per board, and ZipRecruiter's live total of open jobs. At $0.0005 per record, checking 1,000 companies costs $0.50.

How do I filter scraped job postings to only the last 24 or 48 hours?

Each job row carries an exact UTC posting timestamp where the board exposes one, with hour precision on ZipRecruiter, and company records include a posted_last_48h_count. Reposts are flagged separately in a reposted_at field, so a bumped older ad never counts as a genuinely new posting.