ATS Job Scraper & Monitor — Greenhouse, Lever, Ashby +3
Pricing
from $2.00 / 1,000 job postings
ATS Job Scraper & Monitor — Greenhouse, Lever, Ashby +3
Scrape job postings directly from Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee & Workable boards. Monitor mode returns only NEW postings — perfect hiring signals for sales & recruiting.
Pricing
from $2.00 / 1,000 job postings
Rating
0.0
(0)
Developer
Diego Moragues
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
ATS Job Scraper & Monitor — Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee, Workable
This ATS job scraper extracts live job postings directly from the public job boards of Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee and Workable — no browser, no proxies, no LinkedIn scraping. Point it at any list of companies and get clean, structured hiring data in seconds. Enable monitor mode and it becomes a job posting monitor: scheduled runs return only the postings that appeared since the last run — instant hiring signals for sales prospecting, recruiting intelligence and market research.
Why scrape ATS job boards directly?
- Fresher than job aggregators — postings appear here before they reach Indeed or LinkedIn.
- Stable and reliable — these are public JSON endpoints, not fragile HTML scraping.
- Hiring = buying signal. A company hiring "Salesforce Administrator" is buying Salesforce tooling. A company hiring 5 SDRs is scaling sales. Sales teams use this data to time outreach.
- AI-agent ready — flat input, clean JSON output. Works out of the box via MCP for AI agents and LLM pipelines.
What you get for each job posting
{"company": "stripe","ats": "greenhouse","jobId": "gh-7954688","title": "Account Executive, AI Sales","department": "AI GTM Strategy & Solutions","location": "San Francisco, CA","url": "https://stripe.com/jobs/search?gh_jid=7954688","publishedAt": "2026-06-02T08:58:57-04:00","isNew": true,"matchedKeywords": ["sales"]}
How to use it
- Add companies — as plain slugs (
stripe), explicit pairs (lever:haus), or careers-page URLs (https://boards.greenhouse.io/airbnb). The ATS is auto-detected. - (Optional) Add keywords — only jobs matching your keywords (title, department or description) are returned.
- (Optional) Enable monitor mode — and schedule the actor (e.g. daily). Each run returns only NEW postings per company. Combine with a webhook to push new jobs to Slack, email or your CRM.
Use cases
- Sales prospecting: monitor your target account list for hiring signals that indicate budget and initiative.
- Recruiting intelligence: track competitor hiring by department and location.
- Job boards & talent communities: fresh postings for a niche (e.g. "remote React jobs at startups").
- Market research: hiring velocity as a growth indicator for investment analysis.
- AI agents: feed structured hiring data to LLM workflows via the Apify MCP server.
Pricing
Pay per job posting delivered — no subscription, no minimum. You only pay for results.
FAQ
Which ATS platforms are supported?
Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee and Workable. These cover the large majority of startup and mid-market job boards. Missing one you need? Open an issue and it will be added.
How do I find a company's slug?
Usually it's the company name in lowercase (e.g. stripe). If unsure, paste the careers-page URL and the actor extracts it automatically.
Is scraping job boards legal?
The actor only reads the same public JSON endpoints that power each company's own careers page. No login, no personal data, no rate-limit abuse.
How does monitor mode work?
The actor keeps a per-company record of previously seen job IDs in a persistent store. On each run it compares current postings against that record and outputs only new ones (isNew: true).
Can AI agents use this actor?
Yes — the input schema is flat and agent-friendly, and every Apify actor is consumable via the Apify MCP server, so agents can call it as a tool.
What happens if a company isn't found?
You are never charged for it. The company is listed in the NOT_FOUND record of the run's key-value store and in the run log, and the rest of your list continues processing normally.