Community · OAuth Scopes
Community OAuth Scopes
OAuth 2.0
none
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.
MessagingSMSCommunicationsMarketingCreatorsWebhookCompany
Scopes: 0
Flows: authorizationCode
Method: none
OAuth endpoints
Authorization URL
https://oauth-login.community.com/
https://oauth-login.community.com/
Token URL
/oauth/v1/token
/oauth/v1/token
Flows
authorizationCode
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.
The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one.
The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one.
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.