Community · OAuth Scopes

Community OAuth Scopes

OAuth 2.0 derived

Community 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 /oauth/v1/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.

MessagingSMSCommunicationsConversationalMarketingCreatorsWebhooksCompany
Scopes: 0 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://oauth-login.community.com/
Token URL
/oauth/v1/token
Flows
authorizationCode

Scopes (0)

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

Source

OAuth Scopes

Raw ↑
generated: '2026-07-18'
method: derived
source: openapi/community-async-openapi-original.yml
schemes:
- name: oAuth
  source: openapi/community-async-openapi-original.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://oauth-login.community.com/
    tokenUrl: /oauth/v1/token
    tokenUrl_absolute: https://api.community.com/oauth/v1/token
scopes: []
scope_count: 0
docs: null
docs_search:
  checked: '2026-08-13'
  method: >-
    Fetched every page listed in https://developer.community.com/llms.txt as
    markdown and looked for a scopes / permissions reference.
  result: >-
    Community publishes NO OAuth scope or permission reference. The OpenAPI
    oauth2 flow declares an empty scopes map, and the provider's own Python
    Sample Code requests scope=[] when creating the OAuth session
    (https://developer.community.com/reference/sample-code). Access is granted
    per account seat by the Community team rather than by scope, so there is
    nothing to enrich — the empty list is the finding, not a gap in the probe.