Wegalvanize · OAuth Scopes

Wegalvanize OAuth Scopes

OAuth 2.0 searched

Wegalvanize publishes 7 OAuth 2.0 scopes via the authorizationCode, clientCredentials, implicit, refreshToken, and tokenExchange flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Wegalvanize 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.

CompanyGovernanceRiskComplianceAuditGRCAnalyticsAutomationSecurity
Scopes: 7 Flows: authorizationCode, clientCredentials, implicit, refreshToken, tokenExchange Method: searched

Scopes (7)

ScopeDescriptionFlows
openid OpenID Connect authentication; issues an ID token.
profile Access to the user's profile claims (name, locale, timezone, org info).
email Access to the user's email claim.
membership Organization membership / instance association for the user.
config Access to configuration-level claims for the HighBond instance.
offline_access Issue a refresh token for continued (offline) access.
none Explicit no-scope value supported by the authorization server.

📄 Provider scope reference: https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=lp-access-tokens

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://oidc.highbond.com/.well-known/openid-configuration
docs: https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=lp-access-tokens
note: >
  The published OpenAPI declares a single http-bearer scheme (bearerFormat:
  oauth2) with no per-operation scope map, so scopes are not derivable from the
  spec. These scopes are taken verbatim from the HighBond OpenID Connect
  discovery document (scopes_supported). HighBond API tokens are user-bound and
  inherit that user's HighBond permissions rather than being scoped per token.
schemes:
  - name: HighBond OIDC (oidc.highbond.com)
    authorization_endpoint: https://oidc.highbond.com/auth
    token_endpoint: https://oidc.highbond.com/token
    flows: [authorizationCode, clientCredentials, implicit, refreshToken, tokenExchange]
scopes:
  - scope: openid
    description: OpenID Connect authentication; issues an ID token.
  - scope: profile
    description: Access to the user's profile claims (name, locale, timezone, org info).
  - scope: email
    description: Access to the user's email claim.
  - scope: membership
    description: Organization membership / instance association for the user.
  - scope: config
    description: Access to configuration-level claims for the HighBond instance.
  - scope: offline_access
    description: Issue a refresh token for continued (offline) access.
  - scope: none
    description: Explicit no-scope value supported by the authorization server.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set 
curl "https://apis.io/api/v1/scopes/wegalvanize-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.