Reference · built on requestConnectorHR, scheduling & workforce

ADP Workforce Now

Workers, team time cards, time-off balances, pay statements, and event notifications from ADP Workforce Now.

About

ADP Workforce Now is ADP's HR, payroll, and time platform for mid-sized employers in North America. Its developer site publishes a Marketplace API Catalog that groups the product's APIs into HR and payroll, time and labor management, recruiting, and benefit management. Each API guide identifies the worker by an associate OID and describes its REST resources and event APIs.

Through Fibric, an operator reads worker records, team time cards, and time-off requests, listens for event notifications such as worker.hire, and proposes a work schedule change or a time entry correction. You approve the change. It is applied once and recorded.

This is a reference listing. It documents what Fibric would read from ADP Workforce Now and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Worker records through GET /hr/v2/workers and GET /hr/v2/workers/{aoid}, with work assignments as ADP models them
  • A team's time cards through GET /time/v2/workers/{aoid}/team-time-cards, keyed by the manager's associate OID
  • Time-off request summaries for a worker or a team through the Time Off Requests v3 API
  • Time-off balances for an individual or a team through the Time Off Balances v3 API
  • Pay statements for an associate through GET /payroll/v1/workers/{aoid}/organizational-pay-statements
  • Event notification messages such as worker.hire through GET /core/v1/event-notification-messages, or pushed to your webhook endpoint
  • Team work schedules through the Time and Labor Management Work Schedules API

Proposed actions

  • Target capability: propose adding or changing an employee work schedule through the work-schedule.add and work-schedule.change event APIs
  • Target capability: propose a time entry correction through POST /events/time/v2/time-entries.modify
  • Target capability: propose earnings or deductions for a Pay Data batch through POST /events/payroll/v1/pay-data-input.modify
  • Target capability: propose a time-off balance adjustment through POST /events/time/v3/time-off-balances.modify

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Sign off time cards before payroll

    Team time cards arrive through the Team Time Cards API. The operator flags cards with missing entries and proposes a time-entries.modify correction for the manager to approve.

    With Timesheet Signoff

  • Start onboarding on a hire event

    A worker.hire notification lands in the message queue. The operator reads the new worker record and proposes the onboarding checklist and the accounts to create.

    With Onboarding Checklist

  • Catch overlapping leave

    Team time-off request summaries show who is out. When requests overlap on one team, the operator proposes which to approve and records the reason.

    With Leave Conflict

  • Hold overtime before it is worked

    Time cards show hours by day. When a worker nears the threshold you set, the operator proposes a schedule change through the Work Schedules event API.

    With Overtime Guard

Requirements

  • An ADP Workforce Now account with API access, through ADP API Central or an ADP Marketplace developer agreement
  • A client ID and client secret issued by ADP, plus the signed certificate from your certificate signing request
  • Each API added to your project's scope; a 403 means the resource is not in scope
  • Event notifications added to the project under Projects > APIs > Events before hires or changes can be received
Authentication
OAuth 2.0 client credentials at https://accounts.adp.com/auth/oauth/v2/token, sent with the X.509 certificate ADP issues from your certificate signing request; access tokens last one hour.

Limits

  • Event notification messages are retrieved and deleted one at a time; bulk retrieval is not supported
  • Webhook delivery retries at one-minute intervals, then ten more attempts every six hours; failed events are kept for five days
  • Payroll Output APIs are available to ADP Marketplace integrators only, not to Workforce Now clients for direct access
  • A notification is a trigger, not the record; read GET /hr/v2/workers/{aoid} after a worker.hire message

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request ADP Workforce Now ↗

Questions and answers

How does an application authenticate to ADP Workforce Now APIs?
With the OAuth 2.0 client credentials grant. Post grant_type=client_credentials with your client ID and secret as HTTP Basic to https://accounts.adp.com/auth/oauth/v2/token, presenting the X.509 certificate ADP issued. The response carries a Bearer access token that expires in one hour. Send it in the Authorization header on every call.
Does ADP Workforce Now push events?
Yes, two ways. ADP writes event notification messages to a per-subscriber queue that you poll with GET /core/v1/event-notification-messages and delete by adp-msg-msgid. Since October 2025 ADP can also send notifications to your webhook endpoint. Events must first be added to your project scope.
Which time and labor data can be read?
The catalog lists Team Time Cards, Time Off Balances, Time Off Requests, Work Schedules, Data Collection Entries, and Time Entries Modify. Time cards are read per manager through /time/v2/workers/{aoid}/team-time-cards. Time-off request summaries are read per worker or per team through the v3 endpoints.
Ask about ADP Workforce Now

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.