Universal Career Site & ATS Jobs Scraper

Give it company career pages or ATS URLs and get normalized jobs across the major recruiting platforms.

Scrape live jobs from any company website or ATS (Greenhouse, Lever, Ashby, Workday, Workable, SmartRecruiters, Recruitee, Personio, BambooHR and more). Auto-detects the source and finds career pages. No API keys, no login.

All examples below use fictional DEMO-* identifiers, reserved .test domains, and masked contact details. They do not represent real people, listings, products, or companies.

🚀 What this Actor does

• Flexible collection: Direct ATS, Company website discovery, Normalized export, Raw diagnostics.
• Structured output: clean JSON records organized into jobs, errors views.
• Production-ready: concurrency, retries, proxy support, limits, and source-aware diagnostics are exposed through the Actor input.
• Easy automation: run from the Apify Console, API, schedules, webhooks, Make, Zapier, or any HTTP client.

🎛️ Modes and workflows

Mode or workflow	What it does
Direct ATS	Parse job boards from supported ATS providers.
Company website discovery	Start from a company site and locate its public career source automatically.
Normalized export	Map provider-specific payloads into one consistent job schema.
Raw diagnostics	Optionally retain raw data or responses for auditing and custom processing.

💡 Common use cases

• Multi-company job aggregation
• ATS normalization and migration research
• Hiring and talent-market monitoring

📥 Input schema

Configure the Actor in the Input tab or send the same JSON through the API. Fields not needed for your workflow can be omitted.

Field	Type	Description	Default
startUrls required	array	Add company homepages or direct Greenhouse, Lever, Ashby, Workday, Workable, SmartRecruiters, Recruitee, Personio, BambooHR, and other career-page URLs.	—
maxJobsPerSource	integer	Maximum jobs returned from each supplied company. Set to 0 to collect every available job.	0
maxJobsTotal	integer	Global cap across every source after deduplication. Set to 0 for no global limit.	0
includeDescriptions	boolean	Open job-detail endpoints when needed and include both clean text and source HTML descriptions.	true
includeRawData	boolean	Adds rawJson and flattened native__ fields so platform-specific values are never silently discarded.	true
saveRawResponses	boolean	Save successful JSON, HTML, and XML responses in the run key-value store for auditing. Disabled by default to keep storage light.	false
discoverFromCompanyWebsite	boolean	When a normal company homepage is supplied, locate its Careers or Jobs page and detect the underlying ATS.	true
maxDiscoveryPages	integer	Maximum company-site pages checked while searching for its career portal.	5
maxPagesPerSource	integer	Safety limit for unknown or custom career sites. Native ATS integrations still request every available result page.	500
maxConcurrency	integer	Number of sources and job details processed in parallel. The default balances speed and reliability.	10
maxRetries	integer	Retry budget for temporary network and source-server failures.	5
proxyConfiguration	object	Optional Apify or custom proxy configuration for career sites that restrict direct access.	{"useApifyProxy": true}

▶️ Example input

{
  "startUrls": [
    {
      "url": "https://careers.example.test/jobs"
    }
  ],
  "maxJobsPerSource": 100,
  "includeDescriptions": true,
  "discoverFromCompanyWebsite": true
}

📦 Output schema

Each successful item is written to the default dataset. Select a dataset view in the Apify Console or export the full dataset as JSON, CSV, Excel, XML, or RSS.

jobs — 💼 Jobs

Normalized job records.

Fields: company, title, location, department, employmentType, workplaceType, remote, salary, postedAt, expiresAt, ats, jobId, jobUrl, applyUrl, sourceUrl, inputUrl, scrapedAt

errors — ⚠️ Errors

Recoverable failures and source diagnostics.

Fields: ats, errorType, error, inputUrl, sourceUrl, scrapedAt

📤 Example output

{
  "company": "Example Labs",
  "title": "Automation Engineer",
  "location": "Remote",
  "department": "Engineering",
  "employmentType": "Full-time",
  "workplaceType": "Remote",
  "remote": true,
  "ats": "greenhouse",
  "jobId": "DEMO-ATS-JOB-01",
  "jobUrl": "https://careers.example.test/jobs/DEMO-ATS-JOB-01",
  "applyUrl": "https://careers.example.test/jobs/DEMO-ATS-JOB-01/apply"
}

Missing source values are returned as null, empty arrays, or documented availability/status fields; the Actor does not invent unavailable source data.

🔌 API example

Replace the placeholder with an Apify token and send the same input used in the Console:

curl -X POST "https://api.apify.com/v2/acts/trakk~universal-career-site-jobs-scraper/runs?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"startUrls": [{"url": "https://careers.example.test/jobs"}], "maxJobsPerSource": 100, "includeDescriptions": true, "discoverFromCompanyWebsite": true}'

For synchronous integrations, use the run-sync-get-dataset-items API endpoint. For larger jobs, start an asynchronous run and consume its default dataset when the run succeeds.

🧩 Automation and exports

• Schedule recurring runs from the Apify Console.
• Trigger downstream systems with webhooks when a run succeeds or fails.
• Reuse named monitoring keys or stores where the selected workflow supports change tracking.
• Export dataset views to JSON, CSV, Excel, XML, or RSS, or access items through the Apify API.

❓ FAQ

Do I need a login or browser session?

Use only the inputs shown in the Actor schema. If authentication or cookies are supported, the relevant encrypted field is explicitly available in the Input tab; otherwise no account is required.

Why can some fields be empty?

Source pages vary by region, content type, privacy settings, and availability. Optional enrichment also depends on the selected mode. Empty values are preserved honestly instead of being guessed.

How should I run this at scale?

Start with a small representative input, inspect the dataset and cost, then raise item limits and concurrency gradually. Use Apify Proxy when the schema exposes it, and use schedules plus monitoring keys for recurring collection.

Is the example data real?

No. Every example in this README is intentionally fictional and uses demo identifiers, reserved domains, or masked contact values.