Multi-ATS Job Search & Hiring Intelligence API avatar

Multi-ATS Job Search & Hiring Intelligence API

Pricing

from $5.00 / 1,000 ats board checkeds

Go to Apify Store
Multi-ATS Job Search & Hiring Intelligence API

Multi-ATS Job Search & Hiring Intelligence API

Pricing

from $5.00 / 1,000 ats board checkeds

Rating

0.0

(0)

Developer

andre donda de sa

andre donda de sa

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Share

Collect a deterministic current snapshot from known public Greenhouse, Lever, Ashby, SmartRecruiters, and Personio boards. Filter across providers and receive one normalized dataset plus hiring aggregates.

First run

Add board URLs or provider:identifier values and click Start. This Actor is a snapshot/search product: every successful run returns the current matching jobs. It does not discover companies and does not claim to monitor changes.

Output

Each job includes a stable ID, provider and company identity, title, locations, department/team, employment and workplace types only when evidenced, description, public job/apply URLs, timestamps, provenance, and retrieval time. Missing contracted values are null; raw source objects are opt-in. An aggregate row summarizes provider, company, location, title, workplace, and publication distributions.

Safety and limits

Public ATS endpoints only. No browser, proxy, login, AI, or private data. Requests have full-transaction timeouts, retries, streaming byte limits, concurrency limits, pagination limits, and total-job caps. Unsupported ATS products fail during input validation. Failed sources produce explicit diagnostics and are never billed.

Pricing hook

job-emitted fires only after a normalized job is committed to the dataset. Aggregate and diagnostic rows are free. Provisional Store recommendation: $0.0015 per emitted job, subject to private live economics.

See docs/ARCHITECTURE.md, docs/OWNER_RUNBOOK.md, docs/LIVE_VALIDATION.md, and docs/RELEASE_REPORT.md.

Who this Actor is for

Operations, monitoring, research, and data teams that need search and normalize jobs from known public greenhouse, lever and ashby boards. It is designed for scheduled Apify, API, webhook, integration, and MCP-compatible workflows—not for unsupported professional conclusions.

Input reference

  • boards (required): Use public board URLs or provider:identifier values.
  • keywords: Configure Keywords.
  • locations: Configure Locations.
  • titleQuery: Configure Job title contains.
  • maxJobsPerBoard: Configure Maximum jobs per board.
  • maxTotalJobs: Configure Maximum jobs returned.
  • includeRaw: Configure Include source payload per job.
  • maxConcurrency: Configure Concurrent boards.
  • requestTimeoutSecs: Configure Request timeout.
  • maxRequestRetries: Configure Retries.
  • maxResponseBytes: Configure Maximum response bytes.

Representative input (replace placeholders and use only sources you are authorized to access):

{
"boards": [
"greenhouse:stripe"
],
"keywords": [],
"locations": [],
"maxJobsPerBoard": 250,
"maxTotalJobs": 10000,
"includeRaw": false,
"maxConcurrency": 8,
"requestTimeoutSecs": 12,
"maxRequestRetries": 1,
"maxResponseBytes": 8000000
}

Output reference

  • recordType: Structured output field.
  • stableJobId: Structured output field.
  • stableId: Structured output field.
  • provider: Structured output field.
  • company: Structured output field.
  • companyIdentifier: Structured output field.
  • title: Structured output field.
  • locations: Structured output field.
  • department: Structured output field.
  • team: Structured output field.
  • employmentType: Structured output field.
  • workplaceType: Structured output field.
  • description: Structured output field.
  • descriptionText: Structured output field.
  • jobUrl: Structured output field.
  • applyUrl: Structured output field.
  • publishedAt: Structured output field.
  • updatedAt: Structured output field.
  • sourceMetadata: Structured output field.
  • sourceUrl: Structured output field.
  • retrievedAt: Structured output field.
  • raw: Structured output field.
  • aggregateType: Structured output field.
  • jobs: Structured output field.
  • code: Structured output field.
  • message: Structured output field.
  • retryable: Structured output field.

The first complete run creates an expected baseline where the product uses state. Later comparable runs emit only the documented observations or changes. Dataset records retain deterministic identity and source evidence where the contract requires it.

Limitations and known semantics

  • Only the documented source, input forms, fields, identities, and completeness rules are supported.
  • An empty, partial, blocked, timed-out, or malformed upstream response is never silently reported as a successful empty result.
  • Absence or removal is reported only with the exact observational wording and completeness evidence documented by this Actor; it is not proof of a real-world deletion or status unless the source explicitly says so.
  • Upstream publication schedules, schemas, coverage, terms, and availability can change.

Errors and troubleshooting

Check the run status and OUTPUT summary before consuming Dataset rows. For invalid input, correct the named field. For retryable source failures, preserve the monitor key/state and retry later. For schema or completeness failures, do not reset state or infer changes; report the run ID and non-secret diagnostics to support.

API, integrations, and MCP

Run the Actor through the Apify API, Schedule, webhook, or supported integration. Read structured records from the default Dataset and the run summary from the default Key-value store. MCP/agent consumers must preserve source, status, uncertainty, and limitation fields and must not convert observational outputs into unsupported claims.

Submit only data necessary for the documented workflow and only sources you are authorized to access. Do not include credentials, sensitive personal data, or private URLs unless the Actor explicitly documents secure support for them. Outputs are factual automation evidence, not legal, financial, safety, employment, regulatory, or compliance advice. You remain responsible for source rights, downstream use, retention, and professional review.