Fortnite Tracker · Rate Limits

Fortnite Rate Limits

Fortnite Tracker enforces a per-key rate limit of approximately one request every two seconds (i.e. 0.5 requests per second) against api.fortnitetracker.com/v1. Limits are scoped to the TRN-Api-Key issued from fortnitetracker.com/site-api/create — anonymous requests are rejected before rate-limit accounting. There is no separate sandbox/test mode. Higher limits can be requested by contacting Tracker Network support, but the uplift process is informal and not commercially documented. The service has stated "we reserve the right to ban you" — consumers exceeding the documented limit should expect 429 responses and eventual key revocation.

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

It captures 2 rate-limit definitions, measuring requests_per_second and varies.

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

Tagged areas include Rate Limiting, Games And Comics, Fortnite, and Player Statistics.

2 Limits Throttle: 429
Rate LimitingGames And ComicsFortnitePlayer Statistics

Limits

Default per-key rate limit key
requests_per_second · second
0.5
One request per two seconds per TRN-Api-Key. Documented on the Fortnite Tracker site-api landing page.
Negotiated uplift key
varies
see Tracker Network support — granted ad hoc, not publicly documented
Tracker Network historically grants higher limits to legitimate consumers on request. Contact support@tracker.gg or use the feedback site.

Policies

Key-scoped enforcement
All limits attach to the TRN-Api-Key header. Sharing a key across consumers will cause requests to collide at the limit boundary.
Hard rejection at limit
Requests beyond the documented 1 req / 2s rate return HTTP 429. There is no documented soft-burst allowance.
Discretionary key revocation
The site-api landing page explicitly notes the right to ban abusive keys. Repeated 429s or scraping behavior can result in key revocation without notice.
Backoff guidance
Consumers should implement exponential backoff with jitter on 429 responses. There are no documented Retry-After headers — fall back to a fixed 2-second delay between retries.

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