Aflac · OAuth Scopes

Aflac OAuth Scopes

OAuth 2.0 derived

Aflac publishes 6 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Aflac API on a user’s behalf.

Tokens are issued from https://auth.enterprise-connect.aflac.com/oauth/token.

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.

Fortune 500InsuranceSupplemental InsuranceEmployee BenefitsClaimsEnrollmentPolicy AdministrationEnterprise Integration

Scopes: 6 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://auth.enterprise-connect.aflac.com/oauth/token

Flows
clientCredentials

Scopes (6)

Scope	Description	Flows
claims:read	Read claim records	clientCredentials
claims:write	Submit claims	clientCredentials
eligibility:read	Verify eligibility	clientCredentials
enrollment:read	Read enrollment records	clientCredentials
enrollment:write	Create and update enrollments	clientCredentials
groups:read	Read group records	clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

# NOTE added 2026-09-04 by the enrichment pass. These scopes and the tokenUrl below are DERIVED
# from openapi/_ae-authored/ scaffolds written by API Evangelist, not from anything Aflac
# published. Aflac publishes NO OAuth scope reference anonymously, and the host
# auth.enterprise-connect.aflac.com in the tokenUrl resolves NXDOMAIN (checked 2026-09-04).
# Aflac's own documentation states OAuth 2.0 client-credentials is the only supported method but
# does not enumerate scopes. Treat every scope string below as an API Evangelist derivation.
# See authentication/aflac-authentication.yml for the searched, first-party auth profile.
generated: '2026-09-04'
method: derived
source: openapi/aflac-claims-api-openapi.yml, openapi/aflac-eligibility-api-openapi.yml, openapi/aflac-enrollment-api-openapi.yml,
  openapi/aflac-groups-api-openapi.yml, openapi/aflac-policies-api-openapi.yml
schemes:
- name: oauth2
  source: openapi/aflac-claims-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.enterprise-connect.aflac.com/oauth/token
  description: OAuth 2.0 client credentials flow for server-to-server API access.
- name: oauth2
  source: openapi/aflac-eligibility-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.enterprise-connect.aflac.com/oauth/token
  description: OAuth 2.0 client credentials flow for server-to-server API access.
- name: oauth2
  source: openapi/aflac-enrollment-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.enterprise-connect.aflac.com/oauth/token
  description: OAuth 2.0 client credentials flow for server-to-server API access.
- name: oauth2
  source: openapi/aflac-groups-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.enterprise-connect.aflac.com/oauth/token
  description: OAuth 2.0 client credentials flow for server-to-server API access.
- name: oauth2
  source: openapi/aflac-policies-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.enterprise-connect.aflac.com/oauth/token
  description: OAuth 2.0 client credentials flow for server-to-server API access.
scopes:
- scope: claims:read
  description: Read claim records
  flows:
  - clientCredentials
  sources:
  - openapi/aflac-claims-api-openapi.yml
  - openapi/aflac-eligibility-api-openapi.yml
  - openapi/aflac-enrollment-api-openapi.yml
  - openapi/aflac-groups-api-openapi.yml
  - openapi/aflac-policies-api-openapi.yml
- scope: claims:write
  description: Submit claims
  flows:
  - clientCredentials
  sources:
  - openapi/aflac-claims-api-openapi.yml
  - openapi/aflac-eligibility-api-openapi.yml
  - openapi/aflac-enrollment-api-openapi.yml
  - openapi/aflac-groups-api-openapi.yml
  - openapi/aflac-policies-api-openapi.yml
- scope: eligibility:read
  description: Verify eligibility
  flows:
  - clientCredentials
  sources:
  - openapi/aflac-claims-api-openapi.yml
  - openapi/aflac-eligibility-api-openapi.yml
  - openapi/aflac-enrollment-api-openapi.yml
  - openapi/aflac-groups-api-openapi.yml
  - openapi/aflac-policies-api-openapi.yml
- scope: enrollment:read
  description: Read enrollment records
  flows:
  - clientCredentials
  sources:
  - openapi/aflac-claims-api-openapi.yml
  - openapi/aflac-eligibility-api-openapi.yml
  - openapi/aflac-enrollment-api-openapi.yml
  - openapi/aflac-groups-api-openapi.yml
  - openapi/aflac-policies-api-openapi.yml
- scope: enrollment:write
  description: Create and update enrollments
  flows:
  - clientCredentials
  sources:
  - openapi/aflac-claims-api-openapi.yml
  - openapi/aflac-eligibility-api-openapi.yml
  - openapi/aflac-enrollment-api-openapi.yml
  - openapi/aflac-groups-api-openapi.yml
  - openapi/aflac-policies-api-openapi.yml
- scope: groups:read
  description: Read group records
  flows:
  - clientCredentials
  sources:
  - openapi/aflac-claims-api-openapi.yml
  - openapi/aflac-eligibility-api-openapi.yml
  - openapi/aflac-enrollment-api-openapi.yml
  - openapi/aflac-groups-api-openapi.yml
  - openapi/aflac-policies-api-openapi.yml

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/aflac-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.