Authenticate to the Paychex API with client key/secret credentials and retrieve worker records for a company via the Workers resource.
domain: developer.paychex.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an application in Paychex Flex under Company Settings > Connected Applications (as a client) or through the Paychex partner program to receive an API key and secret.
Submit the key and secret in the request body to the Paychex authentication/token endpoint to obtain a bearer access token.
Include the bearer token in the Authorization header of subsequent requests, and re-authenticate before it expires (default 60-minute lifetime, no refresh token available).
Call GET on the companies resource to identify the companyId for the client account you're integrating with.
Call GET on the Workers resource scoped to that company to list worker records.
Call the related sub-resource endpoints (compensation, federal/state taxes, communications) using each returned workerId, since these aren't embedded in the base worker object.
Known gotchas
Credentials for the auth call must go in the request body, not a standard Basic-Auth header — verify the exact parameter placement in the docs before assuming a typical OAuth flow.
Access tokens can't be refreshed; you must re-run the full key/secret authentication call to mint a new one once it expires.
A complete worker profile (compensation, taxes, communications) requires several additional per-worker calls — the base worker record doesn't include them.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?