ADP iHCM
Service ID: adp-ihcm
ADP iHCM (Integrated Human Capital Management) is a comprehensive HCM solution designed for small to medium-sized businesses. It offers a range of services that include payroll, HR, time and attendance, talent management, and benefits administration.
At a Glance
- Difficulty
- 🔧ADVANCEDCustom Auth + Multi-Step Per-Consumer Setup
- Authentication
- OAuth 2.0Client credentials over mutual TLS on ADP's EU infrastructure, not a user-consent flow. Needs an X.509 client certificate, Client ID and Secret.
- Webhooks
- Virtual webhooks↗ - Apideck polls for employee created and updated events
- Partnership Required
- No(The ADP Marketplace Partner Program is a separate route that adds a sandbox and partner API access under a partner agreement; API Central needs no partnership.)
- Apideck Credentials
- Not available(Each consumer provisions their own ADP credentials and certificate.)
- Costs
- Paid by the consumer: ADP bills API Central International as a recurring subscription; prices are shown after signing in. No free trial.
- Sandbox Availability
- Not available(A test instance exists only inside ADP's Marketplace Partner enrollment, which this connection model does not use.)
- Account Type Required
- An ADP iHCM account, ADP's HR and payroll platform outside the US and Canada, with ADP API Central enabled.
- Consumer Access Level
- An ADP administrator who can enable API Central for the account and obtain the certificate and credentials.
- Rate Limits
- 120 requests/minute per API Central project and a maximum of 10 concurrent requests; ADP returns HTTP 429 beyond either limit.
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Enable ADP API Central on the iHCM account | Share requirements | ✓ | — |
| Obtain the certificate and credentials from ADP | — | ✓ | — |
| Enter credentials in Vault | Implement Vault | ✓ | — |
| Authorize connection | — | ✓ | Mints the OAuth token over mutual TLS |
| Replace the certificate before it lapses | Prompt the consumer | ✓ | — |
| Build via the Unified API | ✓ | — | Maintains the connector |
| Connection sync | — | — | ✓ Polls via virtual webhooks |
| Monitor connections | ✓ Via the Apideck Dashboard | Can revoke credentials or the certificate | Logs and alerts |
Environments
- Single environment
- ADP iHCM uses one set of consumer-provisioned credentials: Client ID, Client Secret, client certificate and client key. There is no separate sandbox with its own credentials. To test, use an ADP iHCM account that has API Central enabled. Apideck cannot supply temporary shared test credentials for this connector, because it has no Apideck-hosted sandbox app. Take care when testing against live payroll and HR data.
🚨Important to Know About ADP iHCM
- An iHCM subscription alone never yields credentials: the consumer must have ADP API Central enabled first. Plan for that decision landing inside your onboarding flow rather than before it.
- Consumers in the US or Canada are not on iHCM: ADP sells Workforce Now there, which Apideck supports through a separate connector. Confirm which ADP platform a consumer runs before pointing them at this one.
- The connection depends on a client certificate and stops working the moment it lapses: a dated, per-connection failure that lands long after the build is finished.
- You cannot de-risk this build before a consumer commits: your first end-to-end test necessarily runs against that consumer's live iHCM tenant.
⚠️
4 gotchas across 4 resources
Connector-specific behaviors and limitations to be aware of
📦
5 supported resources
View field mappings, supported operations, and schema details