AccelByte · Rate Limits

Accelbyte Rate Limits

AGS enforces per-environment, per-service rate limiting at the API gateway. Limits are applied per client/IP and per endpoint and are tuned per customer environment and plan; high-volume ingestion services (Game Telemetry) and authentication (IAM token) are the most commonly throttled surfaces. Exact numeric limits are environment-specific and not published as a single public table, so they are not reconciled in this artifact.

Accelbyte Rate Limits is the machine-readable rate-limit profile for AccelByte on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests and events.

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

Tagged areas include Gaming, Backend, BaaS, Live Services, and Rate Limiting.

4 Limits Throttle: 429
GamingBackendBaaSLive ServicesRate LimitingQuotasThrottling

Limits

IAM Token Requests client
requests
see provider documentation
OAuth2 token issuance is rate limited per client to protect the auth service.
Per-Service Requests client
requests
see provider documentation
Each AGS service (Cloud Save, Statistics, Platform, etc.) has its own gateway limit.
Game Telemetry Ingestion client
events
see provider documentation
Telemetry endpoints accept batched events; ingestion is throttled per environment.
Matchmaking Tickets client
requests
see provider documentation
Ticket submission is limited to protect the matchmaking pipeline.

Policies

Environment-Scoped Limits
Limits are provisioned per customer environment and per namespace and can be increased on enterprise plans.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Batching
Prefer batched/bulk endpoints (e.g., bulk stat updates, batched telemetry) to stay within request limits.

Sources