ADP API

Name: ADP API
Brand: ADP API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingPayrolloauth29 EndpointsREST

For Agents

Retrieve ADP worker rosters, pay statements, time cards, organisation data, and job applicants, and subscribe to hire and termination events through OAuth 2.0 with client certificates.

Install Jentic One Beta

Connect the ADP API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ADP API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ADP API.

List active workers and retrieve a worker's full profile by ADP Object Identifier (AOID)

Retrieve pay statements for a worker to power payroll auditing or self-service apps

List time cards for a worker for time-and-attendance reporting and approvals

GET STARTED

Start building with ADP API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ADP API for, with concrete tasks.

★ Workforce Roster Sync

HRIS integrators sync the active worker roster from ADP into downstream systems like provisioning tools, identity providers, and Slack onboarding bots using GET /hr/v2/workers and GET /hr/v2/workers/{aoid}. The API returns ADP's canonical worker record so downstream systems trust it as the source of truth for employee status.

Pull the full active worker list via GET /hr/v2/workers and upsert each worker into Okta by AOID

Payroll Statement Self-Service

Employee self-service portals expose pay statements pulled from GET /payroll/v1/workers/{aoid}/pay-statements without rebuilding ADP's pay-stub UI. The endpoint returns a worker's recent pay statements scoped by AOID so apps render historical pay-stub lists with one call per worker.

Fetch the last 12 pay statements for worker AOID 123ABC and render them in the employee self-service portal

Joiner-Mover-Leaver Automation

IT and ops teams subscribe to ADP worker hire and termination events via POST /events/hr/v1/worker.hire and POST /events/hr/v1/worker.terminate to trigger account provisioning and deprovisioning automatically. This closes the loop between HR system-of-record and identity infrastructure without nightly batch jobs.

Subscribe to worker.terminate events via POST /events/hr/v1/worker.terminate and route them to the deprovisioning workflow

Agent-Driven HR Operations via Jentic

AI agents can pull worker, pay, and time data through Jentic without handling ADP's OAuth 2.0 plus mutual-TLS handshake themselves. Jentic stores the OAuth credentials and client certificate in the vault and presents the agent with simple intent-based search instead of ADP's auth complexity.

Search Jentic for 'adp pay statement', load GET /payroll/v1/workers/{aoid}/pay-statements, and execute it for AOID 123ABC

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for the adp api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/hr/v2/workers

List workers

GET

/hr/v2/workers/{aoid}

Get worker by AOID

GET

/payroll/v1/workers/{aoid}/pay-statements

List pay statements

GET

/time/v2/workers/{aoid}/time-cards

List time cards

GET

/staffing/v2/job-applicants

List job applicants

POST

/events/hr/v1/worker.terminate

Subscribe to termination events

GET

/hr/v2/workers

List workers

GET

/hr/v2/workers/{aoid}

Get worker by AOID

GET

/payroll/v1/workers/{aoid}/pay-statements

List pay statements

GET

/time/v2/workers/{aoid}/time-cards

List time cards

GET

/staffing/v2/job-applicants

List job applicants

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your ADP OAuth client secret and SSL client certificate are stored once, encrypted, by your own Jentic One instance, which performs the mutual-TLS handshake at execution time. Neither the secret nor the certificate enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get an adp pay statement' or 'list adp workers', and Jentic returns the matching ADP operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using ADP API through Jentic.

Why is there no official OpenAPI spec for the ADP API?

ADP publishes documentation at developers.adp.com but does not ship an OpenAPI specification. Jentic generates and maintains this spec from the published developer portal so AI agents and developers can call it via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the ADP API use?

ADP uses OAuth 2.0 client-credentials authentication paired with an SSL client certificate issued by ADP. Both the OAuth token and the certificate must be presented on every request. Through Jentic, the client certificate and OAuth credentials are held in the vault and never enter the agent's prompt context.

Can I retrieve pay statements with the ADP API?

Yes. GET /payroll/v1/workers/{aoid}/pay-statements returns pay statements for a worker keyed by their ADP Object Identifier. This is the canonical endpoint for surfacing pay history in self-service apps.

How do I subscribe to ADP worker termination events through Jentic?

Search Jentic for 'adp worker terminate event', load POST /events/hr/v1/worker.terminate, and execute it with the subscription payload. Termination events feed deprovisioning automation without nightly batch reconciliation.

What are the rate limits for the ADP API?

ADP enforces per-tenant rate limits documented in the developer portal but not present in the OpenAPI spec. Expect HTTP 429 responses if you exceed them and apply exponential backoff. Through Jentic, retries with backoff can be configured in the execution request.

Can I list job applicants with the ADP API?

Yes. GET /staffing/v2/job-applicants returns the applicants in the recruiting pipeline for ATS integrations. Combine this with worker.hire events to track the full pipeline from applicant to onboarded worker.

Can I limit what my agent is allowed to do with the ADP API?

Yes. Because you run Jentic One yourself, your own rules decide which ADP operations and credentials the agent may use. Since ADP puts the worker aoid in the URL path, such as /hr/v2/workers/{aoid}/pay-statements, you can pin the agent to a single worker so it reads only that worker's pay statements and time cards and nothing else. You also choose the operations it may call, so a write action like POST /events/hr/v1/worker.terminate stays out of reach unless you explicitly allow it.