Micro Connect · OAuth Scopes
Micro Connect OAuth Scopes
OAuth 2.0
probed
Micro Connect publishes 10 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Micro Connect API on a user’s behalf.
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.
CompanyFinancial ServicesCapital MarketsExchangeRevenue-Based FinancingFintechInvestingSmall BusinessHong KongMacaoChina
Scopes: 10
Flows:
Method: probed
Scopes (10)
| Scope | Description | Flows |
|---|---|---|
| openid | Required OpenID Connect scope; requests an ID token. | |
| profile | Standard OIDC profile claims (name, given_name, family_name, preferred_username). | |
| Standard OIDC email claim. | ||
| phone | Standard OIDC phone_number claims. | |
| address | Standard OIDC address claim. | |
| roles | Keycloak built-in scope; adds realm and client role mappings to the token. | |
| web-origins | Keycloak built-in scope; adds allowed CORS origins to the token. | |
| offline_access | Requests an offline refresh token. | |
| microprofile-jwt | Keycloak built-in scope; adds MicroProfile JWT claims (upn, groups). | |
| acr | Authentication Context Class Reference; realm advertises acr_values 0 and 1. |
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.