Granicus · OAuth Scopes
Granicus OAuth Scopes
OAuth 2.0
none
Granicus 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.
CompanyGovernmentGovTechPublic SectorCitizen EngagementDigital CommunicationsSoftware-as-a-Service
Scopes: 0
Flows:
Method: none
Scopes (0)
Granicus 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.
No OAuth2 scopes documented for Granicus APIs. Authentication uses API tokens (X-AUTH-TOKEN header) rather than OAuth.
No OAuth2 scopes documented for Granicus APIs. Authentication uses API tokens (X-AUTH-TOKEN header) rather than OAuth.
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.