Paychex · OAuth Scopes

Paychex OAuth Scopes

OAuth 2.0 derived

Paychex uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://api.paychex.com/auth/oauth/v2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

BenefitsHCMHRPaychex FlexPayrollTime and AttendanceWorkforceFortune 1000

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.paychex.com/auth/oauth/v2/token

Flows
clientCredentials

Scopes (0)

Paychex implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Paychex uses an OAuth 2.0 client_credentials flow with access granted per registered partner application and company rather than requestable scopes; the public docs (https://developer.paychex.com/getting-started/authentication) publish no scopes reference, showing scope values (read:company_people write:company_people read:workers) only inside a sample token response with no descriptions.

📄 Provider scope reference: https://developer.paychex.com/getting-started/authentication

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/paychex-payroll-companies-openapi.yml, openapi/paychex-time-openapi.yml, openapi/paychex-workers-openapi.yml
docs: https://developer.paychex.com/getting-started/authentication
note: >-
  Paychex uses an OAuth 2.0 client_credentials flow with access granted per registered
  partner application and company rather than requestable scopes; the public docs
  (https://developer.paychex.com/getting-started/authentication) publish no scopes
  reference, showing scope values (read:company_people write:company_people read:workers)
  only inside a sample token response with no descriptions.
schemes:
- name: oauth2ClientCredentials
  source: openapi/paychex-payroll-companies-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.paychex.com/auth/oauth/v2/token
- name: oauth2ClientCredentials
  source: openapi/paychex-time-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.paychex.com/auth/oauth/v2/token
- name: oauth2ClientCredentials
  source: openapi/paychex-workers-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.paychex.com/auth/oauth/v2/token
scopes: []

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/paychex-developer-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.