Multi-ATS Jobs Search Scraper

This Actor collects public ATS job postings. The verified default path is Greenhouse: a Greenhouse board URL is resolved to the official boards-api.greenhouse.io JSON endpoint with content=true, then normalized into complete rich job records. The repository also retains platform-specific legacy handlers for other ATS selections.

Greenhouse input

The default local input searches the public Fivetran Greenhouse board:

{
  "atsPlatform": "auto",
  "mode": "search",
  "companyUrl": "https://boards.greenhouse.io/fivetran",
  "searchQuery": "engineer",
  "maxItems": 3,
  "maxRequests": 1,
  "requestTimeoutMs": 15000,
  "deadlineMs": 60000,
  "maxRetries": 1
}

Search filters every word in searchQuery against the published title, company, location, departments, and offices. Greenhouse single and multiple modes select exact job IDs or exact public job URLs from the same official board response. maxItems, maxRequests, requestTimeoutMs, deadlineMs, and maxRetries keep the direct path bounded. includeDescription=false removes description content after complete-record validation.

Output

Greenhouse rows contain source-backed identity, employer, locations, departments, offices, metadata, employee type, sanitized description text and HTML, headings, sections, list items, salary ranges, dates, compliance fields, canonical job URL, source API URL, request receipts, field coverage, and quality metrics. The source payload is retained as sourceData and sourceRecord after contact-field redaction. applyUrl is emitted only when Greenhouse publishes a distinct application URL; the job page is never mislabeled as an application URL.

Run evidence is written to the default key-value store:

• RUN_SUMMARY
• RUN_DIAGNOSTICS
• RUN_REQUESTS
• RUN_HEALTH
• RUN_METADATA

Local QA

npm ci --ignore-scripts --no-audit --no-fund
npm run check
npm test
npm run lint
npm run validate
npx --yes apify-cli validate-schema .actor/input_schema.json
npx --yes apify-cli run --purge --input-file INPUT.json

The verified Greenhouse path uses native HTTPS and Cheerio; it does not use a browser, proxy, mirror, login, CAPTCHA solver, or stealth bypass. It runs locally and on the Apify platform. Optional platform handlers remain bounded legacy fallbacks and are not claimed as live-verified by the default Greenhouse QA run.

Cost and responsible use

maxItems, maxRequests, per-request timeouts, retries, and a run deadline bound source traffic and compute use. Start with the defaults and increase limits only when necessary. Scrape public job data responsibly, respect applicable site terms and laws, and do not use the Actor to collect private or access-controlled data.