HiringCafe Jobs Scraper (ATS-sourced jobs, filters, alerts)

HiringCafe collects openings straight from company career pages and applicant tracking systems (Workday, Greenhouse, Lever, Ashby, BambooHR, PeopleAdmin, Zoho and hundreds more) instead of re-listing job-board ads. This actor reads HiringCafe's recently-posted feed, keeps the postings that match your keywords and countries, and returns each one as a flat row with the employer's own apply link.

What this actor does and does not do

• Discovery is the recently-posted feed, filtered by keyword and location — the jobs HiringCafe added in roughly the last day (a few hundred postings, three pages of 200). It is not a search over HiringCafe's full index of tens of thousands of openings.
• Why: hiringcafe.com/robots.txt disallows the site's own search URLs (Disallow: /*?searchState=*, Disallow: /*?page=*) and allows /recently-posted-jobs and /job/. This actor reads only the allowed routes.
• What that makes it good at: a daily feed of brand-new openings for your keywords, which is exactly what monitor mode is for. What it is not good at: back-filling every job that ever matched a term.

What you get

One row per posting: id/jobId, url, title, company, companyDomain, location, isRemote, workplaceType, employmentType, seniority, jobCategory, salaryMin, salaryMax, salaryCurrency, postedAt, applyUrl, ats, dedupId, description, query, page, rank, source, scrapedAt.

dedupId is HiringCafe's own cluster id for an opening (<ats>___<board token>___<posting id>): the same job re-posted on another board carries the same dedupId, so it is what you group or de-duplicate on across runs, while id stays unique per posting.

The feed itself carries only title, company, location, jobCategory and postedAt. Everything else — apply link, salary, employment type, seniority, remote flag, description — comes from the job page, which is why Fetch job pages is on by default. It costs one extra request per kept job; turn it off for a fast, cheap title-and-company list.

Example output

One full row (Fetch job pages on):

{
  "id": "mwhcioxukzkehm06",
  "url": "https://hiringcafe.com/job/business-specialist-iii-university-of-idaho-moscow-idaho-mwhcioxukzkehm06",
  "title": "Business Specialist III",
  "company": "University of Idaho",
  "companyDomain": "uidaho.edu",
  "location": "Moscow, Idaho, United States",
  "isRemote": false,
  "workplaceType": "Onsite",
  "employmentType": "Full Time",
  "seniority": "Mid Level",
  "jobCategory": "Finance and Accounting",
  "salaryMin": 57200.0,
  "salaryMax": 57200.0,
  "salaryCurrency": "USD",
  "postedAt": "2026-09-13T18:17:37.000Z",
  "applyUrl": "https://uidaho.peopleadmin.com/postings/52742",
  "ats": "peopleadmin",
  "dedupId": "peopleadmin___uidaho_com___52742",
  "query": "business specialist",
  "rank": 37
}

More rows from the example dataset:

title	company	location	salaryMin–salaryMax	ats
Revenue Audit Supervisor	Rain Rock Casino	Yreka, California, United States	49920–62400 USD	saashr
Business Specialist III	University of Idaho	Moscow, Idaho, United States	57200 USD	peopleadmin
Health Technician (Phlebotomy)	Department of Veterans Affairs	Appleton, Wisconsin, United States	—	—

Use cases

• New-job alerts. Run it daily in monitor mode on your keywords and get a webhook or Telegram message for every new opening, with the apply link already in the row.
• Fresh ATS leads. ats and applyUrl tell you which system a company just posted through — a live signal for anyone selling to recruiters.
• Salary tracking on new postings. salaryMin/salaryMax are filled only when the employer published a range, so the numbers are real, not estimates.

Input

Field	Meaning	Default
searches	Keywords to keep; every word of a line must appear in title, company or category	["manager"]
locations	Country names or ISO-2 codes (country level only)	empty = all
remoteOnly	Keep only remote jobs (switches job pages on)	false
postedWithinDays	Drop postings older than this many days	empty
maxPages	Feed pages to scan, 200 postings each (1-25)	5
fetchDetails	Open each kept job's page	true
maxItems	Stop after this many rows	100
mode	scrape or monitor (only new/changed since last run)	scrape
monitorStateId, webhookUrl, telegramBotToken, telegramChatId	Monitor-mode state key and alert targets	empty

Pricing

Event	Price
result	$0.0008 per job ($0.80 per 1,000)
monitor-check	$0.005 per monitor run
change	$0.0008 per new/changed job

You are charged only for rows actually pushed. Postings dropped by your filters — including the remote-only filter, which is applied after the job page is read — are never pushed and never charged. No proxy is needed, so there is no proxy surcharge.

Why this actor

• Robots-respecting. Only the routes hiringcafe.com/robots.txt allows are read; the site's own search URLs are not touched.
• The employer's own apply link, not a redirect through an aggregator.
• Honest salaries — a range appears only when the employer published one; HiringCafe's internal estimate is never passed off as a real range.
• Monitor mode with webhook and Telegram alerts for new jobs on a keyword.
• An empty run is explained, not guessed. The RUN_SUMMARY record separates "no posting matched your keywords" from "the source refused the request", and refusals push nothing and charge nothing.

Limits

• The feed is the scope. Only recently posted jobs are visible — currently around 600 postings across three pages, refreshed daily. A keyword with no fresh postings returns nothing; that is an answer, not a failure.
• Keyword matching is a whole-word match over title, company and category — it is not HiringCafe's semantic search. manager matches "Kitchen Manager" but not "Management"; short words behave sanely (it does not match "Substitute", rn does not match "Intern").
• The country filter reads the last segment of the posting's location text, so a posting that names no country there ("New York City +3 more", "Huntingtown or Prince Frederick") is dropped even though it may be in the country you asked for.
• postedAt comes from the feed when the age filter runs, and is then refined by the job page, which uses HiringCafe's estimated publish date. A row can therefore end up with a postedAt slightly outside the window you asked for.
• Without Fetch job pages there is no apply link, salary, seniority, employment type, remote flag or description.
• No applicant, recruiter or viewer data is collected — the source exposes per-user activity on each posting and this actor never reads it.

FAQ

Can I search HiringCafe's whole index? Not with this actor. robots.txt disallows the search URLs, so discovery is the recently-posted feed. For ongoing coverage of a keyword, run it daily in monitor mode — over a week you accumulate every new posting that matched.

Do I need a proxy? No. The source answers the platform directly; the actor retries the occasional anti-bot interstitial by itself.

Why did I get fewer rows than maxItems? The feed had fewer matching postings, or maxPages capped the scan, or a filter removed them. The RUN_SUMMARY record in the run's key-value store carries emptyReason.

Is the apply link a redirect? No. applyUrl is the URL on the employer's own career site or ATS.

Does it return personal data? No. Rows are job-level and company-level only.

Changelog

• 0.1: initial release — recently-posted feed with keyword, country, remote and age filters, job-page enrichment, monitor mode; an anti-bot interstitial is retried and then reported as a block instead of an empty dataset.

---

If this actor saved you time, a short review on its Store page genuinely helps other people find it. Found a bug or need a field that is missing? Open a ticket on the Issues tab.