BeatAPI · OAuth Scopes
BeatAPI OAuth Scopes
OAuth 2.0
none
BeatAPI 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.
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.
CompanyAIPlatformUnified-APIData-Integration
Scopes: 0
Flows:
Method: none
Scopes (0)
BeatAPI 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.
Provider uses API key authentication; no OAuth scopes documented.
Provider uses API key authentication; no OAuth scopes documented.
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.