Authenticate using the ADP OAuth 2.0 client_credentials flow with mTLS as required by ADP; obtain and store the access token.
Retrieve the target employee's associate OID (the stable unique identifier used by ADP APIs) from the Workers API before constructing schedule payloads.
Construct a schedule payload using the schema defined in the TLM Work Schedules API Guide, specifying the employee associate OID, schedule pattern, effective dates, and work rule.
POST or PUT the schedule payload to the work schedules endpoint; the API accepts schedule updates for one or more employees per call depending on the endpoint.
Confirm success via the response status and any returned schedule identifiers; store these for future updates or deletions.
Test thoroughly in the ADP sandbox environment before writing schedules to production, as schedule errors can affect payroll calculations.
Known gotchas
ADP's work schedule APIs have limited support on ADP Workforce Now Next Generation versus the standard Workforce Now platform; verify endpoint availability for the specific ADP product version.
Schedule effective-date logic is strict: overlapping or gap date ranges may be rejected or silently create unexpected schedule configurations.
The associate OID is distinct from the employee file number (personnel ID); using the wrong identifier type results in record-not-found errors.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp