Aflac · Rate Limits

Aflac Rate Limits

Aflac Enterprise Connect enforces rate limiting at the AWS API Gateway stage on every path and HTTP method of every service. Limits are configured per path + method in an optional apispec/aws/config.yaml, and where a service sets nothing, a default is applied automatically from the service's architectural layer. What Aflac does NOT publish is the actual numbers, the response headers, or the status code on exhaustion — so a caller cannot predict or detect throttling from the documentation alone.

Aflac Rate Limits is the machine-readable rate-limit profile for Aflac on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests.

Limit state is signalled in the published, headers, and note response headers, and an exhausted limit returns HTTP not published.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include Rate Limiting, Insurance, and AWS API Gateway.

3 Limits Exhausted: HTTP not published publishedheadersnote
Transcribed from the provider's documentation on 2026-09-04 — docs.enterprise-connect.aflac.com/docs/developer-guide/ap....
View Source
Rate LimitingInsuranceAWS API Gateway

Limits

Per-path, per-method throttle endpoint
requests · per not published
not published/not published
"The path and http method specified in the config.yaml file must be included in your open api specification." The limit is therefore bound to a declared OpenAPI operation, not to a route pattern.
Layer-based default endpoint
requests
not published
"Rate limiting is enabled on all paths and HTTP methods. You do not need to specify a burstLimit or rateLimit per path and method, a sensible default will be applied based on your application level (aspect/process/system/experience/core)." The five layers are the same prefixes used in AEC service naming — a-, p-, s-, e-, c-.
Quotas account
requests
not published
Quotas are configurable alongside throttles, in the same AWS API Gateway mechanism.

Policies

Best-effort, not a ceiling
Aflac states plainly that "both throttles and quotas are applied on a best-effort basis and should be thought of as targets rather than guaranteed request ceilings."
Purpose
"It helps prevent abuse, ensures fair usage, and maintains API performance ... This in turn helps protect the user experience in systems like MyAflac."
Testable by design
The platform simulator service e-aec-test is deliberately configured with extremely low limits so throttling can be triggered in automated tests, exposing a worked path /v1/i-am-rate-limited. Aflac notes it is "unlikely you'd set this low a limit in production".

Sources

Work with this as data

Every rate limit 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 rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit 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 rate limit 
curl "https://apis.io/api/v1/rate-limits/aflac-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?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.