aflac
Aflac is America's leading provider of supplemental insurance, offering products that pay benefits when a policyholder experiences an accident, illness, or injury. Aflac provides REST APIs through its Enterprise Connect (AEC) platform enabling benefits technology companies, HR platforms, and benefits administrators to integrate supplemental insurance enrollment, policy management, and claims capabilities into their workflows.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles aflac the way a machine reads it — 71 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — aflac scores 55.7/100 (developing), with a separate agent-readiness read of 55/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile aflac
Each block below is one kind of artifact we hold for aflac. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Aflac Claims API
The Aflac Claims API provides programmatic access to supplemental insurance claim submission, status retrieval, and benefit payment tracking. It enables policyholders and admini...
aflac Claims API
Claims submission and status retrieval operations.
aflac Eligibility API
Employee eligibility verification operations.
aflac Enrollment API
Benefits enrollment operations for supplemental insurance products.
aflac Groups API
Employer group management operations.
aflac Policies API
Policy management and retrieval operations.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Aflac Enterprise Connect API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Aflac Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Aflac Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Aflac Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Electronic Benefits Enrollment
Replace EDI 834 file-based enrollment with real-time API-driven enrollment workflows for supplemental insurance products.
Policy Administration
Manage group and individual supplemental insurance policies including enrollments, terminations, and coverage changes.
Claims Submission
Enable digital claim filing for supplemental insurance products including accident, critical illness, cancer, and disability coverage.
Eligibility Verification
Verify employee eligibility for Aflac supplemental insurance products in real time during enrollment.
Benefits Administration Integration
Connect benefits administration platforms with Aflac's enrollment and policy systems via standardized REST APIs.
Real-Time Enrollment Confirmation
Receive immediate enrollment confirmation and policy numbers upon successful enrollment submission.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Aflac Enterprise Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
aflac API Rules
SPECTRALaflac API Rules
SPECTRALJSON Schema 13
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ClaimList
JSON SCHEMAClaimRequest
JSON SCHEMAClaim
JSON SCHEMADependent
JSON SCHEMAEligibilityRequest
JSON SCHEMAEligibilityResponse
JSON SCHEMAEnrollmentList
JSON SCHEMAEnrollmentRequest
JSON SCHEMAEnrollment
JSON SCHEMAGroupList
JSON SCHEMAGroup
JSON SCHEMAPolicyList
JSON SCHEMAPolicy
JSON SCHEMAScroll within the panel for all 13 ·
JSON Structure 13
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Enterprise Connect Claim List Structure
JSON STRUCTUREEnterprise Connect Claim Request Structure
JSON STRUCTUREEnterprise Connect Claim Structure
JSON STRUCTUREEnterprise Connect Dependent Structure
JSON STRUCTUREEnterprise Connect Eligibility Request Structure
JSON STRUCTUREEnterprise Connect Eligibility Response Structure
JSON STRUCTUREEnterprise Connect Enrollment List Structure
JSON STRUCTUREEnterprise Connect Enrollment Request Structure
JSON STRUCTUREEnterprise Connect Enrollment Structure
JSON STRUCTUREEnterprise Connect Group List Structure
JSON STRUCTUREEnterprise Connect Group Structure
JSON STRUCTUREEnterprise Connect Policy List Structure
JSON STRUCTUREEnterprise Connect Policy Structure
JSON STRUCTUREScroll within the panel for all 13 ·
Examples 13
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 13 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
HR Platform Integration
HR and benefits administration platforms integrate with Aflac's API to offer supplemental insurance enrollment within their existing benefits workflows.
Employer Self-Service Enrollment
Employers manage supplemental insurance enrollments for employees during open enrollment periods via connected benefits platforms.
Claims Tracking
Employees and HR teams track the status of Aflac supplemental insurance claims submitted after a qualifying health event.
Benefits Broker Workflow
Benefits brokers manage group policy setup, employee enrollment, and plan changes for employer clients through integrated tools.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Employee Navigator
Aflac connects with Employee Navigator benefits administration platform for automated enrollment data exchange.
Benefitfocus
Integration with Benefitfocus benefits marketplace for supplemental insurance enrollment.
ADP
Payroll and HR integration with ADP for Aflac premium deduction and enrollment synchronization.
Workday
Enterprise HR platform integration for benefits enrollment and Aflac policy administration.
bswift
Benefits administration platform integration for Aflac group enrollment.
Resources
Every other property we hold for aflac — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 14
Reference material describing how the API behaves
Scroll within the panel for all 14 ·
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 16
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 16 ·
Build 14
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 14 ·
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/aflac · machine-readable index on apis.io