The discord.place API enforces rate limits on all endpoints to ensure fair usage for every developer. When you exceed your allowance, the API returns aDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/discordplace/discord.place/llms.txt
Use this file to discover all available pages before exploring further.
429 Too Many Requests response.
Response Headers
Every API response includes the following headers so you can track your current rate-limit window:The maximum number of requests allowed in the current window.Example:
10The number of requests remaining in the current window.Example:
9Time in seconds until the rate-limit window resets and your allowance is restored.Example:
60429 Response Body
When you exceed the limit, the API responds with:Handling Rate Limits
Read the
ratelimit-remaining header on every response. When it reaches 0, pause requests until ratelimit-reset seconds have elapsed rather than waiting for a 429 error.429, implement exponential backoff before retrying:
Per-Endpoint Limits
Rate limits are applied per endpoint. The limits currently in effect are:| Endpoint | Limit |
|---|---|
PATCH /bots/{id}/stats | 2 requests per 120 minutes |
GET /bots/{id}/voters/{user_id} | 100 requests per 5 minutes |
The
PATCH /bots/{id}/stats limit is intentionally low. Call this endpoint on a timer (e.g., every hour) rather than on every guild event to stay well within the window.
