Mutual of America Life Insurance Company OAuth Scopes

OAuth 2.0 probed

Mutual of America Life Insurance Company publishes 7 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Mutual of America Life Insurance Company 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.

InsuranceLife InsuranceRetirementFinancial ServicesPensionsAnnuitiesWealth ManagementIdentity
Scopes: 7 Flows: Method: probed

Scopes (7)

ScopeDescriptionFlows
openid Required for OpenID Connect; requests an ID token.
email Email address and email_verified claims.
profile Default profile claims (name, family_name, given_name, locale, zoneinfo…).
address End-user postal address claim.
phone phone_number and phone_number_verified claims.
offline_access Requests a refresh token for long-lived sessions.
groups Group membership claim, used to drive portal entitlements.

Source

OAuth Scopes

mutual-of-america-life-insurance-scopes.yml Raw ↑
generated: '2026-08-28'
method: probed
source: https://login.mutualofamerica.com/.well-known/openid-configuration
issuer: https://login.mutualofamerica.com
note: >-
  Read verbatim from `scopes_supported` in the two discovery documents saved under well-known/.
  IMPORTANT READING NOTE: the OpenID Connect document advertises the standard OIDC scope set
  and nothing bespoke — Mutual of America has defined no product scopes of its own, because it
  ships no public API. The RFC 8414 document additionally advertises the full `okta.*`
  management scope set; those are the identity vendor's platform-administration scopes present
  on every Okta org authorization server, NOT scopes Mutual of America authored or exposes to
  third parties. They are recorded here for completeness and marked `vendor_platform: true` so
  they are never mistaken for a Mutual of America API surface.
scope_count: 7
scopes:
  - name: openid
    description: Required for OpenID Connect; requests an ID token.
  - name: email
    description: Email address and email_verified claims.
  - name: profile
    description: Default profile claims (name, family_name, given_name, locale, zoneinfo…).
  - name: address
    description: End-user postal address claim.
  - name: phone
    description: phone_number and phone_number_verified claims.
  - name: offline_access
    description: Requests a refresh token for long-lived sessions.
  - name: groups
    description: Group membership claim, used to drive portal entitlements.
vendor_platform_scopes:
  vendor_platform: true
  source: https://login.mutualofamerica.com/.well-known/oauth-authorization-server
  count: 82
  note: >-
    Okta org-management scopes (okta.users.*, okta.groups.*, okta.apps.*, okta.policies.*,
    okta.logs.read, okta.apiTokens.*, …) advertised by the Okta org authorization server.
    Reachable only by administrators of the tenant. Not a Mutual of America API product.
docs: null
docs_note: >-
  No scopes/permissions reference page is published. Mutual of America has no developer portal.

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/mutual-of-america-life-insurance-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.

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