ADP API

Name: ADP API API
Brand: ADP API
Availability: InStock

★ Only Publicly Available SpecHR 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.

Quickstart

Get started with ADP API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list active workers from ADP"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with ADP API 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

List organisation departments and work locations to keep downstream systems in sync

GET STARTED

Start building with ADP API API

Explore with Jentic

View OpenAPI Spec

Use for: I need to retrieve all active workers from ADP, Get the most recent pay statement for worker AOID 123ABC, List time cards for worker 123ABC for the last pay period, List all organisation departments in the company

Not supported: Does not handle benefits enrolment UI, expense management, or learning management — use for HR worker, payroll, time, organisation, recruiting, and worker-event data only.

Jentic publishes the only available OpenAPI specification for ADP API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for the ADP API, keeping it validated and agent-ready. The ADP API exposes 9 endpoints across HR, payroll, time and attendance, organisation data, recruiting, and worker lifecycle events. Use it to retrieve worker rosters, pay statements, time cards, organisation departments, work locations, and job applicants, and to subscribe to worker hire and termination events. Authentication is OAuth 2.0 with mutually authenticated SSL client certificates issued by ADP.

Use Cases

Patterns agents use ADP API 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 though Jentic?

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

Credential isolation

ADP requires OAuth 2.0 plus an SSL client certificate. Both the OAuth client secret and the certificate are stored encrypted in the Jentic vault. The agent never receives either — Jentic performs the mutual-TLS handshake at execution time.

Intent-based discovery

Agents search Jentic by intent (e.g., 'adp pay statement' or 'list adp workers') and Jentic returns the matching ADP endpoint with its input schema. The agent does not need to navigate developers.adp.com to find the right call.

Time to first call

Direct ADP integration: 1-2 weeks because of the certificate-issuance and OAuth ceremony plus per-endpoint testing. Through Jentic: under a day once the certificate has been uploaded — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Workday API

Workday's HCM API covering workers, payroll, and recruiting.

Choose Workday when the company runs Workday as its HRIS; choose ADP when ADP is the system of record for HR and payroll.

Alternative

Gusto API

Modern payroll and HR API for small and mid-sized businesses.

Choose Gusto for SMB payroll workflows; choose ADP for enterprise HCM with more comprehensive worker, time, and event coverage.

Complementary

BambooHR API

HRIS often paired with ADP-managed payroll for employee record management.

Use BambooHR for the employee record and lifecycle UI; pair with ADP for payroll execution and pay-stub data.

FAQs

Specific to using ADP API 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 at https://app.jentic.com/sign-up.

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.