Rate limits & caching

Rate limiting

Rates are limited; however, the margins are generous. This is to avoid misconfigured clients and to ensure the service is available for every client. The rates are based on IP. If for some reason a client violates the rate limit, we return a 429 HTTP response code (Too Many Requests).

Fair use

We have rate limiting in place, but so far it has never been an issue for any of our customers. Its goal is to prevent abuse.

Some rules of thumb:

1. Only update information you actually need
2. Use the in operator to fetch several items in one go (keep in mind that there is a technical limit to URL length), see Filtering & sorting

Update interval

Below is an overview of the resources, whether you can cache them locally, and how often we suggest to update them.

Resource	Suggested update interval	What could change	Cache locally
Tournament	Monthly	End date	✅
Venue	Monthly	Minor details	✅
Team	Monthly	Fixes in team naming	✅
Event	Daily	Date confirmation, exact start and end date	✅
Tickets	directly	Available tickets, prices, status	❌ - changes too often you risk being out-of-date
Category	Weekly	Descriptions	✅

Keep alive

We have a specific endpoint to check our system health, rate-limited at 1 request per second. Please use this endpoint if you want to monitor the availability of our systems to avoid rate limits.

For the uptime of all our services, see the status page. Our availability targets are described under Service levels.

Next steps

• Errors & validation
• Welcome & data model