Globacap · OAuth Scopes
Globacap OAuth Scopes
OAuth 2.0
probed
Globacap 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.
CompanyPrivate Capital MarketsCapital MarketsSecuritiesFinancial-ServicesFintechTokenizationShare RegisterSecondary MarketsUnited Kingdom
Scopes: 0
Flows:
Method: probed
Scopes (0)
Globacap 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.
These are the scopes the Globacap identity provider advertises in its anonymous OpenID Connect discovery document. They are the standard OIDC scope set — Globacap publishes no API-specific or product-specific permission reference, and no scopes/permissions documentation page exists to enrich this from. Do not read this as an API authorization model; it is the login surface only.
These are the scopes the Globacap identity provider advertises in its anonymous OpenID Connect discovery document. They are the standard OIDC scope set — Globacap publishes no API-specific or product-specific permission reference, and no scopes/permissions documentation page exists to enrich this from. Do not read this as an API authorization model; it is the login surface only.
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.