Limits
The numbers below are the ones in force on this site right now.
| What is counted | Limit |
|---|---|
| All calls of an app in development or in review | 120 per minute |
| All calls of a public app | 1.200 per minute |
| Calls on behalf of one member | 60 per minute |
| Writes on behalf of one member (scores, activity) | 10 per minute |
| Token requests (code, refresh) | 30 per minute |
Also: at most 5 apps per developer, 25 testers and 5 leaderboards per app.
Headers
Every response carries X-RateLimit-Limit and X-RateLimit-Remaining. When you go over a limit you get 429 and a Retry-After header with the number of seconds:
{
"error": "rate_limited",
"message": "Too many requests. Try again in 21 s.",
"retry_after": 21
}
Wait retry_after seconds before the next call. Do not retry at once.
Automatic suspension
An app that keeps going over its limit is suspended automatically and you get a notification with the reason. No token works for a suspended app. When you have fixed the cause, contact the administrators to lift the suspension.
Error shape
All errors of the public API have the same shape:
{ "error": "error_code", "message": "Text for the developer" }
In code, compare the error field. The text in message may change.
| HTTP | error |
Meaning |
|---|---|---|
| 401 | invalid_token |
the token is missing, expired, or access was removed |
| 403 | insufficient_scope |
the token lacks the scope for this call (the name is in the scope field) |
| 403 | forbidden |
the action is not allowed |
| 404 | not_found |
it does not exist, or the signed-in member may not see it |
| 422 | validation_failed |
invalid data, per-field errors are in errors |
| 429 | rate_limited |
too many requests, see retry_after |
| 500 | server_error |
an error on our side, try later |
A validation error example:
{
"error": "validation_failed",
"message": "The score field must be an integer.",
"errors": { "score": ["The score field must be an integer."] }
}
Response shape
- A successful response carries its data in the
datafield. - Dates are ISO 8601 with a time zone, for example
2026-11-15T19:42:07+00:00. - A field the member does not show on their profile is
null. - New fields may be added without notice. We do not change or remove existing fields without a new API version.