# ADP Jobs Scraper (`scrapyx/adp-jobs-scraper`) Actor

Scrapes job listings from jobs.adp.com, the careers site of ADP, one of the largest payroll/HR platforms in the US. Optionally filter by team; returns job title, url, posted date, location and the full description, address list and employment type.

- **URL**: https://apify.com/scrapyx/adp-jobs-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.35 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## ADP Jobs Scraper

Scrapes job listings from **[jobs.adp.com](https://jobs.adp.com)** — the
careers site of ADP, one of the largest payroll/HR/HCM platforms in the US.
A different source than the job boards this portfolio already covers
(Indeed, Glassdoor, JobStreet, Bayt, HeadHunter, Reed): these are ADP's own
open roles, not third-party-aggregated listings.

Public data only. No login, no cookies, no browser.

### What you get

Two record types share one dataset, told apart by `recordType`.

#### `JOB` — one row per listing

Search rows (`listing`) carry job id, title, url, a posted-date preview and
a location summary. With **Fetch full job details** on (the default), each
row also gets a `jobDetails` object — the complete Schema.org `JobPosting`:
full HTML description, employment type, and a structured list of every
office/remote location the role is open to (each with a full postal
address).

#### `SEARCH_SUMMARY` — one row per query

How many pages were fetched and how many jobs were returned.

### Input

| Field | What it does |
| --- | --- |
| **Team / department filter** | optional list of ADP's own category names (e.g. `Sales`); verified to actually filter |
| **Max jobs / max pages per query** | pagination caps |
| **Fetch full job details** | off = fast listing-only crawl |

#### Example

```json
{
  "teams": ["Sales", "Finance/Accounting"],
  "maxItems": 200,
  "includeJobDetails": true
}
```

### Notes on reliability

- **No WAF challenge.** Serves data cold on every TLS profile tested.
- **Runs unattended.** No human-captured session, no expiring token.
- **`teams` filter is real, not a silent-widen trap.** A bogus team value
  returns zero jobs (verified live), not the unfiltered baseline —
  unusual among filter parameters found across this portfolio, most of
  which DO silently widen.
- **Pagination verified genuine**, not a repeat/clamp: page 1 and page 2
  return zero overlapping job ids.
- **Residential proxy by default** on cloud runs.
- **Failures never vanish.** A job withdrawn mid-crawl degrades that one
  row (`_detailError`); every input maps to at least one output row.

### A markup gotcha worth knowing

The detail page's JSON-LD script tag HTML-entity-encodes its own `type`
attribute — `application/ld+json`, not a literal `application/ld+json`
— which silently breaks a naive regex/selector looking for the standard
string. This actor anchors on the script's stable `id="js-job-posting"`
instead. See [`CRAWLING_METHOD.md`](CRAWLING_METHOD.md) for the full trail.

### Output envelope

Every record carries `_input`, `_source` and `_scrapedAt`. Upstream field
names pass through **verbatim** under `listing` (search) and `jobDetails`
(detail) — no renaming. `_source` is `S1-html-search` for listing-only rows
and `S1-html-search+S2-jsonld-detail` once details are attached.

# Actor input Schema

## `teams` (type: `array`):

Optional. ADP's own department/category names (e.g. 'Sales', 'Finance/Accounting') -- verified to actually filter results (a bogus value returns zero jobs, not the unfiltered baseline). Leave empty to crawl all open roles. Multiple entries run as independent queries, each with its own SEARCH\_SUMMARY row.

## `maxItems` (type: `integer`):

Stop paginating a query after this many jobs. Set to 0 for unlimited (still bounded by Max pages).

## `maxPages` (type: `integer`):

Hard cap on pagination depth. No upstream ceiling was discovered this session (pagination nav showed 9 pages on an unfiltered search but was not bisected further) -- this is the actor's own safety valve.

## `pageSize` (type: `integer`):

ADP's own default is 20.

## `includeJobDetails` (type: `boolean`):

Fetch the complete Schema.org JobPosting (full HTML description, structured multi-location address list, employment type) for each result via one extra request per job. Turn this off for a fast listing-only crawl -- search rows already carry title, url, posted-date preview and a location summary.

## `maxConcurrency` (type: `integer`):

Upper bound on requests in flight at once, across pagination and detail fetches.

## `proxyConfiguration` (type: `object`):

jobs.adp.com runs no active bot challenge and a direct connection worked cleanly across every probe this session, but Residential is the default for cloud runs -- container egress is a different posture than a home connection, and this portfolio has lost a full cloud run to that difference before.

## Actor input object example

```json
{
  "teams": [],
  "maxItems": 200,
  "maxPages": 25,
  "pageSize": 20,
  "includeJobDetails": true,
  "maxConcurrency": 4,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/adp-jobs-scraper").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/adp-jobs-scraper").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 '{}' |
apify call scrapyx/adp-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/adp-jobs-scraper"
        }
    }
}
```

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/jMki2B3gPE3Arst23/builds/PPAxPgOcaSk3dUYSq/openapi.json