ADP

This page records how composerID publishes into ADP: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. ADP Workforce Now is a payroll-anchored HRIS system of record for the permanent-hiring channel. composerID posts the hire through the Applicant Onboard V2 API, carries the Intent ID in a worker custom field, and closes the loop by subscribing to worker event notifications.

Category: HRIS / HCM. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation).

Integration path

How composerID connects to this destination, at a glance.

Step	Detail
Authentication	OAuth 2.0 client credentials plus a mutual-TLS client certificate on every call (certificates requested and rotated in the API Central portal); OpenID Connect underneath.
composerID publishes	Applicant Onboard: Applicant Onboard V2 API (in-progress or completed hire)
Intent ID lands on	`worker` `customFieldGroup.intentId`, written into the destination record
Back-sync	Webhooks: the destination pushes events; composerID verifies each delivery and lands it on the intent’s timeline.

Vendor documentation

ADP API guides (developers.adp.com)

Workforce Now API catalog

API Central for Workforce Now

API posture

Aspect	Detail
Authentication	OAuth 2.0 client credentials plus a mutual-TLS client certificate on every call (certificates requested and rotated in the API Central portal); OpenID Connect underneath. Access itself is provisioned - API Central is a purchasable add-on per client, or a Marketplace partner agreement.
Style	REST, JSON, event-message envelopes for writes; canonical URIs must be added to the app’s scope in the Consumer Application Registry before an API is callable
Base URL	https://api.adp.com (tokens from https://accounts.adp.com)
Webhooks	Event notifications - subscribe to worker events (hire, change, terminate) to trigger back-sync pulls.
Events posture	Webhooks
Rate limits	Per-subscription throttling; hire processing is slow (can exceed 20s and time out at the gateway) - design submits as async with status polling.
Objects	Applicant Onboard V2, Workers v2 (reads; SSN/birth masked unless masked=false), Workers Life Cycle Management (start/cancel hire, change hire date), custom fields (category 3), validation tables, event notifications

Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.

Applicant Onboard

Post the hire into WFN

Mapping	Detail
Canonical to destination	person, job/position, department, start_date, pay group
Target	Applicant Onboard V2 API (in-progress or completed hire)
Requirement	Required
Notes	The older Worker Hire Event API (/events/hr/v1/worker.hire) is deprecated - target V2

Worker record + custom fields

Enrich and read back

Mapping	Detail
Canonical to destination	associateOID, assignment, cost identifiers
Target	Workers v2 + custom-field APIs (category 3)
Requirement	Tenant
Notes	Sensitive fields are masked by default

Intent ID + hire back-sync

Correlate and reconcile

Mapping	Detail
Canonical to destination	intent_id (worker custom field); worker.hire notifications
Target	Custom field + event-notification subscription
Requirement	Required
Notes	Onboard processing is async in practice - reconcile on the event, not the response

Everything is provisioned: the client buys API Central (or you integrate as a Marketplace partner), each API’s canonical URI is added to the application’s registry scope, and calls need the mTLS certificate as well as the bearer token. Templates and mandatory fields (Group, state tax fields) vary per WFN configuration - preflight against the /meta endpoints. Most reference documentation sits behind the developer login.

Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.

⌘I

Get started

Concepts

Guides

Destinations

Upstream connectors

API reference

Endpoints

Manuscript API (Triage)

Manuscript endpoints

Resources

Integration path

Vendor documentation

ADP API guides (developers.adp.com)

Workforce Now API catalog

API Central for Workforce Now

API posture

Publish target and field mapping

Next steps

How composerID connects

Publishing

All destinations

​Integration path

​Vendor documentation

ADP API guides (developers.adp.com)

Workforce Now API catalog

API Central for Workforce Now

​API posture

​Publish target and field mapping

​Next steps

How composerID connects

Publishing

All destinations

Integration path

Vendor documentation

API posture

Publish target and field mapping

Next steps