ADP API: the developer’s reality check
ADP runs payroll and HR for over a million businesses, so “ADP API” is one of the most-searched terms in HR tech. The API exists and the documentation is public - but the credentials are not. Here is what each surface covers, who can actually get access, and where job-postings data fits.
On this page
The short answer
The ADP API is a real, documented, actively maintained platform - and it is closed. Documentation lives at developers.adp.com and anyone can read it. Credentials are issued only to two groups: ADP clients, for their own account’s data, and software vendors approved into the ADP Marketplace partner program. There is no self-serve API key, no free tier, no developer sandbox you can enter with just an email address.
If you searched “ADP API” hoping to read job postings, payroll data, or worker records across companies: that product does not exist. What exists is a per-client integration surface, plus - for job postings specifically - a public per-company careers layer this guide covers in the second half.
The ADP API landscape
ADP is not one product, and neither is its API. The developer portal organizes APIs by platform, and the differences matter:
- ADP Workforce Now - the mid-market HR suite, and the platform most integrations target. APIs cover workers, payroll, time, benefits, and recruiting.
- RUN Powered by ADP - the small-business payroll product, with a narrower API surface aimed at accounting and payroll integrations.
- ADP Vantage and enterprise platforms - large-enterprise HCM with integration surfaces that are even more relationship-managed.
- The ADP Marketplace - the partner program and app store. Vendors that want to sell an integration to ADP’s customer base integrate and certify here.
All of these share one data model rule: every credential is scoped to one ADP client. The API is a pipe between a company and its own ADP data, not a window into ADP’s customer base.
Getting access: OAuth, certificates, partners
ADP’s authentication is stricter than most SaaS APIs, which reflects what the data is - payroll and HR records:
- OAuth 2.0 client-credentials - tokens are issued per client relationship, not per user.
- Mutual TLS - requests present a certificate issued through ADP’s onboarding, in addition to the OAuth token. No certificate, no calls.
- Relationship-gated issuance - clients request access through their ADP representative; vendors go through Marketplace partner onboarding and certification. Both paths take weeks, not minutes.
The practical consequence: tutorials that end with “then grab your API key” do not apply here. Plan access as a procurement step, not a signup step.
The Workforce Now API
Since ADP Workforce Now API is the surface most people actually mean, its shape in brief: REST endpoints under ADP’s API gateway covering HR (worker records, demographics, employment status), payroll, time and attendance, benefits, and the recruiting module. Responses follow ADP’s common data model, so worker objects look consistent across products.
The recruiting endpoints deserve a caveat, because they sound like a jobs API: they cover one company’s requisitions, applications, and hiring workflow - the employer’s own pipeline, for the employer’s own systems. They are the right tool for syncing an HRIS or building internal hiring dashboards, and the wrong tool for anything that needs postings across companies.
Where ADP job postings actually live
Companies that run recruiting on ADP publish their openings to an ADP-hosted career center - a public careers site on ADP infrastructure with a per-company URL. These pages are ordinary public web pages: any candidate can browse them, and so can any crawler that knows the URL.
That makes ADP-hosted postings readable in principle, with the usual aggregation catches: there is no directory of career-center URLs, the page structure is built for candidates rather than parsers, and nothing about the surface is stable by contract. Reading one company’s postings is an afternoon of work. Reading all of them - discovery, parsing, freshness, dedup - is an infrastructure project, and it is why ADP sits high on every jobs-data provider’s source roadmap: an enormous share of US mid-market employers hire through it.
What to do, by goal
- You are an ADP client automating your own HR or payroll. Request API access through your ADP representative, budget time for the certificate setup, and build against the Workforce Now documentation at developers.adp.com.
- You are a vendor selling to companies that run ADP. The ADP Marketplace partner program is the path - it is sales-led and certification-gated, and it is also the only door.
- You need job postings from ADP-hosted career centers. Per company, read the public career center directly. At aggregation scale, use a jobs-data layer instead of building discovery and parsing yourself. JobsPipe’s sources page documents exactly which ATS platforms we cover today - Workday, Greenhouse, Lever, iCIMS, Ashby, and 30+ more - each with the same normalized schema.
- You wanted payroll or worker data across companies. That is not a product ADP or anyone else legitimately sells through an API. Treat any offer of it with suspicion.
Need postings data without the partner-program wait? 30+ sources, one schema, free tier.
Get a free API keyFAQ
Is there a public ADP API?+
No self-serve one. ADP's APIs are real and well documented at developers.adp.com, but credentials are only issued to ADP clients (for their own account) and to partners approved into the ADP Marketplace program. There is no path to an API key without one of those relationships.
How do I get ADP API credentials?+
Two paths. As an ADP client, you request API access for your own account through your ADP representative and receive OAuth client credentials plus a certificate for mutual TLS. As a software vendor, you apply to the ADP Marketplace partner program, integrate against ADP's sandbox, and get certified before receiving production credentials. Both are relationship-gated processes, not sign-up forms.
Where is the ADP API documentation?+
developers.adp.com hosts the API Central documentation: the API directory by product (Workforce Now, Vantage, Run, and others), the OAuth 2.0 and certificate authentication guides, and per-endpoint references. You can read most documentation without credentials; you cannot call anything without them.
What is the ADP Workforce Now API?+
The API surface for ADP's mid-market HR platform: workers, payroll, time, benefits, and the recruiting module. Authentication is OAuth 2.0 client-credentials with mutual TLS, and every token is scoped to one client account. Recruiting endpoints cover that one company's requisitions and applications - they are not a cross-company jobs feed.
Does ADP have a job postings API?+
Not a public cross-customer one. Job postings created in ADP's recruiting products are published to each company's own career center - hosted pages on ADP infrastructure with per-company URLs. Those pages are public and readable per company, but ADP exposes no endpoint that aggregates postings across its customer base.
How do I get job postings from companies that use ADP?+
Per company, read its public ADP-hosted career center like any careers page. Across many companies, someone has to discover each career center URL and parse each site - the aggregation-layer work that jobs-data APIs exist to do. JobsPipe normalizes postings from 30+ ATS and job-board sources into one schema; our sources page documents current coverage.
Related