Help Scout · OAuth Scopes

Help Scout OAuth Scopes

OAuth 2.0 derived

Help Scout 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.helpscout.net/v2/oauth2/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.

Customer SupportHelp DeskEmailLive ChatKnowledge BaseSaaS

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.helpscout.net/v2/oauth2/token

Flows
clientCredentials

Scopes (0)

Help Scout 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.

Help Scout's Mailbox API OAuth 2.0 (authorization code and client credentials flows) does not define or document any OAuth scopes; access is governed by the authorizing user's Help Scout account permissions (https://developer.helpscout.com/mailbox-api/overview/authentication/).

📄 Provider scope reference: https://developer.helpscout.com/mailbox-api/overview/authentication/

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/helpscout-openapi.yml
docs: https://developer.helpscout.com/mailbox-api/overview/authentication/
note: Help Scout's Mailbox API OAuth 2.0 (authorization code and client credentials
  flows) does not define or document any OAuth scopes; access is governed by the
  authorizing user's Help Scout account permissions (https://developer.helpscout.com/mailbox-api/overview/authentication/).
schemes:
- name: oauth2
  source: openapi/helpscout-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.helpscout.net/v2/oauth2/token
scopes: []