RUN Powered by ADP
Service ID: adp-run
RUN Powered by ADP® small business web-based payroll software solution handles the nitty-gritty, so you can focus on running your business.
Beta — this connector is in beta. Functionality and resource coverage may change.
At a Glance
- Difficulty
- 🔧ADVANCEDADP Marketplace Partnership + Security Review + Custom Auth
- Authentication
- OAuth 2.0Client credentials over mutual TLS, not a user-consent flow. Credentials are held once for your integration, not per connection.
- Webhooks
- Virtual webhooks↗ - Apideck polls for employee created and updated events
- Partnership Required
- Yes(ADP offers no API Central for RUN, so the ADP Marketplace Partner Program is the only route to RUN data; joining provides sandbox access.)
- Partnership Application
- ADP Marketplace Partner Program↗
- Apideck Credentials
- Not available(You supply your own ADP credentials.)
- Costs
- ADP publishes no fee: partner terms are a negotiated revenue share, on your side rather than your consumer's. No add-on for them to buy.
- Sandbox Availability
- Available(Provided once you are enrolled as an ADP Marketplace partner.)
- Account Type Required
- A RUN Powered by ADP account in the United States; RUN is ADP's small-business product, aimed at roughly 1 to 49 employees.
- Consumer Access Level
- A RUN administrator with authority to add an app to the account and grant it consent.
- Rate Limits
- 300 requests/minute per integration project and a maximum of 50 concurrent requests; ADP returns HTTP 429 beyond either limit.
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Enroll in the ADP Marketplace Partner Program | ✓ | — | — |
| List your app on ADP Marketplace | ✓ | — | — |
| Subscribe to the app and grant consent | Guide your consumer | ✓ | — |
| Supply your ADP credentials to Apideck | ✓ | — | — |
| Build via the Unified API | ✓ | — | Maintains the connector |
| Connection sync | — | — | ✓ Polls via virtual webhooks |
| Monitor connections | ✓ Via the Apideck Dashboard | Can revoke consent | Logs and alerts |
Environments
- Single environment
- Testing and production share the same credentials, so there is no separate sandbox environment to point at. Once you are enrolled on ADP Marketplace you can request a test instance from ADP's Partner Self-Service Portal, which is the same route that reaches production data. Take care when testing against live payroll and HR data.
🚨Important to Know About RUN Powered by ADP
- This connector is in beta and has never been verified against a live RUN account: it was mapped from ADP's documentation alone. Treat connectivity and field-level behaviour alike as unproven, and prove both on your own tenant before committing to a build.
- Enrolling is a real gate, not a form: ADP requires a signed Developer's Participation Agreement and puts your integration through a security review that includes a penetration test.
- Consumer onboarding happens in ADP Marketplace, not in your product: each consumer must add your listed app there before any of their data can be read, and you cannot do that step on their behalf.
- Check which ADP product a prospective consumer actually runs before scoping this connector. Those on ADP Workforce Now or ADP iHCM need a different route entirely, and Apideck supports both as separate connectors.
⚠️
1 gotcha across 1 resource
Connector-specific behaviors and limitations to be aware of
📦
1 supported resource
View field mappings, supported operations, and schema details