# ATS Detector: Careers Page and Job Board Finder (`edgef-4/careers-page-detector`) Actor

Which ATS does a company use? For sales teams and recruiting tool builders: find careers page, job board URL, proof. $3.00 per 1,000 boards found, misses free. ATS lookup of 14 applicant tracking systems: detect Greenhouse, Lever, Workday, Ashby. Reads no postings; hiring-signals counts roles.

- **URL**: https://apify.com/edgef-4/careers-page-detector.md
- **Developed by:** [Edge](https://apify.com/edgef-4) (community)
- **Categories:** Jobs, Lead generation, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 job board founds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

Which ATS does a company use? For sales teams and recruiting tool builders: find careers page, job board URL, proof. $3.00 per 1,000 boards found, misses free. ATS lookup of 14 applicant tracking systems: detect Greenhouse, Lever, Workday, Ashby. Reads no postings; hiring-signals counts roles. Try it: run the prefilled input (https://www.figma.com) and open the ATS and job boards found table. An ATS detector and careers page finder.

**Price (pay per event):** $0.003 per job board found ($3.00 per 1,000 boards found), plus the platform's $0.00005 start event per run. Sites with no board, blocked sites and errors have no per-site charge.

**What it does not do:** Does not read or count job postings: give board_url to hiring-signals for that.

**Quickstart** (with your Apify token):

- API: `curl -X POST "https://api.apify.com/v2/acts/edgef-4~careers-page-detector/run-sync-get-dataset-items" -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" -d '{"urls":["figma.com"]}'`
- MCP `call-actor`: `{"actor":"edgef-4/careers-page-detector","input":{"urls":["figma.com"]}}`
- Python: `ApifyClient(os.environ["APIFY_TOKEN"]).actor("edgef-4/careers-page-detector").call(run_input={"urls":["figma.com"]})`

### What it does

Give it company sites; for each it finds the careers page and the hosted job board behind it.
It names the ATS platform (the applicant tracking system) and the board, and quotes the exact link, frame or script address that proves it.
For Greenhouse, Lever, Ashby and SmartRecruiters it also returns a ready input for a job board reader.

### Who uses it

- Sales and research teams who turn a list of company sites into a list of job boards to watch.
- Recruiting tool builders who need to know which applicant tracking platform a company uses.
- Analysts who measure platform share across a set of companies.

### Input

| Field | Type | Default | What it does |
|---|---|---|---|
| `urls` | list of text | required | Company sites or domains, for example `example.com` or `https://www.example.com/` |

### Output

One record per site. Sample record (SYNTHETIC: example.com data, not a real company):

```json
{
  "id": "site:www.example.com",
  "site": "https://www.example.com/",
  "careers_url": "https://www.example.com/careers/",
  "platform": "greenhouse",
  "board_slug": "examplecorp",
  "board_url": "https://boards.greenhouse.io/examplecorp",
  "evidence": "https://boards.greenhouse.io/examplecorp/jobs/4000001",
  "evidence_kind": "link",
  "confidence": "high",
  "reader_input": {"platform": "greenhouse", "slug": "examplecorp"},
  "source_url": "https://www.example.com/careers/",
  "fetched_at": "2026-10-07T18:00:00Z",
  "status": "ok",
  "error": null,
  "error_detail": null
}
```

Field rules: `evidence` is the address exactly as written in the page at `source_url`. `confidence` is `high` for a link or a frame and `medium` for a script. `careers_url` is the link that clearly means the company's own jobs: a link text such as Careers, Jobs, Join us or We are hiring, or a careers word as a whole part of the path or of the host name. A product page about career sites is not taken. When links about careers were seen but none is clear, `careers_url` stays empty and the `not_found` record has `confidence` `low`. A site where no platform address was found has `status` `not_found`; `blocked` means the site did not let the Actor read the homepage, and `error` says which case it is: `robots_disallow` when its robots.txt disallows the homepage, `blocked` when the site refused the request with HTTP 401, 403 or 429 or with a bot challenge (`error_detail` then starts with "the site refused the request" and names the answer); an address that is not a public site, or a site that cannot be read, is `error` with the reason. A robots.txt that answers with a 4xx status other than 429 counts as no rules (RFC 9309). A robots.txt that cannot be read (a 5xx status, a 429, a timeout, a network failure or a redirect to another site) gives `status` `error` with `error` `robots_unreadable`, and the site is not read; it is never called a disallow. A host name that does not resolve gives `status` `error` with `error` `dns_failure`.

Platforms (14): Greenhouse, Lever, Ashby, SmartRecruiters, Workable, Recruitee, Personio, Teamtailor, BambooHR, JazzHR, Breezy HR, Workday, Jobvite, Pinpoint.

### What a run costs

The price is $3.00 per 1,000 sites where a platform was found, plus the platform's start fee of $0.00005 per run (charged once, because the Actor runs with at most 1 GB of memory). Checking 1,000 sites in which 600 boards are found costs $1.80005. Sites without a detection, blocked sites and errors are not charged.

### Limits and what it will not do

- Per site it reads the homepage and, when it is on the same host or its www form, the careers page, each with its redirects inside those two hosts (at most 5 hops), plus robots.txt once for each of the two hosts it actually requests: three requests for a site without redirects, five when the homepage redirects to the www form. robots.txt is asked before every request and every redirect hop. A careers page on another host is recorded in `careers_url` and never fetched.
- It matches link, frame and script addresses only. A page that names a platform in its text is not a detection.
- A service or marketing host under a platform's domain (such as `www`, `landing`, `support`, `docs`, `academy` or `trust`) is never reported as a board. On the site of a platform vendor itself, links to its platform domain count as its own pages: only its careers link can name its board.
- A site that redirects to another domain is reported as an error, because only the site's own host and its www form are requested.
- It follows robots.txt and never works around a block. No login, no cookies, no proxies, no browser: a board drawn by scripts after the page loads is found only through its script address.
- It identifies itself as `edge-careers-page-detector/0.2` in every request. A site owner can block it in robots.txt with `User-agent: edge-careers-page-detector` and `Disallow: /`. It never pretends to be a browser.
- It does not read the job postings themselves, and it collects no data about people.

### Source and terms

- The sites you list are read as any visitor would, with robots.txt obeyed and at most 2 requests per second per site. Check that the sites you list allow this.
- Platform addresses are matched by host and path patterns of the public board pages of each platform.
- This Actor is not affiliated with any of the 14 platforms or with the companies whose sites it reads.

### Questions and answers

**Why `not_found` on a site I know uses a platform?** The careers page may load the board with a script the Actor does not run, or link it from a page deeper than the careers page. The `careers_url` field shows where it looked.

**What is `reader_input`?** An item you can paste into the `boards` list of a job board reader that reads Greenhouse, Lever, Ashby and SmartRecruiters.

**Does it follow the careers link to another domain?** No. It records the address and matches it against the platform rules without requesting it.

**Which languages does it understand for the careers link?** English, German, French, Spanish, Italian, Dutch, Portuguese, Polish, Finnish and Swedish link texts and paths.

**Is a script detection as good as a link?** It is marked `medium`: the script proves the platform and the board name, but not that the page lists open roles.

# Changelog

This Actor's version history is a separate document: https://apify.com/edgef-4/careers-page-detector/changelog.md

# Actor input Schema

## `urls` (type: `array`):

Company sites or bare domains, one per line, for example figma.com or https://www.example.com/. Required, up to 1,000 per run; the same site twice is read once. Per site it reads robots.txt, the homepage and the careers page when that page is on the same host or its www form (a careers page on another host is recorded in careers_url, not fetched). A site that redirects to another domain comes back as error.

## Actor input object example

```json
{
  "urls": [
    "https://www.figma.com"
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

The dataset: one row per company site with the careers page, the ATS platform, the job board URL and the evidence address. Only rows with status ok are charged.

## `summary` (type: `string`):

The RUN_SUMMARY record of the default key-value store: rows by status, errors by type, charged events, requests per host and seconds per site.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://www.figma.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("edgef-4/careers-page-detector").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": ["https://www.figma.com"] }

# Run the Actor and wait for it to finish
run = client.actor("edgef-4/careers-page-detector").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://www.figma.com"
  ]
}' |
apify call edgef-4/careers-page-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,edgef-4/careers-page-detector"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/K7KURSrmqfnFqmbYP/builds/Luzjjp97GsVHVKzMo/openapi.json