Paradox · OAuth Scopes

Paradox OAuth Scopes

OAuth 2.0 derived

Paradox 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 /auth/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.

Artificial IntelligenceCandidate ScreeningChatbotConversational AIHiring AutomationHR TechnologyInterview SchedulingRecruitingSMSTalent Acquisition

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
/auth/token

Flows
clientCredentials

Scopes (0)

Paradox 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.

Paradox does not publish OAuth scopes; the API uses an OAuth 2.0 client credentials flow (or Basic auth) with an account ID and secret key issued by the Paradox Integrations Team, with no scope parameter documented (https://readme.paradox.ai/reference/authentication).

📄 Provider scope reference: https://readme.paradox.ai/reference/authentication

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/paradox-api-openapi.yml
docs: https://readme.paradox.ai/reference/authentication
note: >-
  Paradox does not publish OAuth scopes; the API uses an OAuth 2.0 client
  credentials flow (or Basic auth) with an account ID and secret key issued by
  the Paradox Integrations Team, with no scope parameter documented
  (https://readme.paradox.ai/reference/authentication).
schemes:
- name: oauth2
  source: openapi/paradox-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /auth/token
  description: OAuth 2.0 client credentials authentication
scopes: []