Skip to main content
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 a 429 Too Many Requests response.

Response Headers

Every API response includes the following headers so you can track your current rate-limit window:
integer
required
The maximum number of requests allowed in the current window.Example: 10
integer
required
The number of requests remaining in the current window.Example: 9
integer
required
Time in seconds until the rate-limit window resets and your allowance is restored.Example: 60

429 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.
If you do receive a 429, implement exponential backoff before retrying:

Per-Endpoint Limits

Rate limits are applied per endpoint. The limits currently in effect are:
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.

Requesting a Rate Limit Exemption

If your use case requires higher throughput than the default limits allow, contact the discord.place team at support@discord.place or reach out on the Discord server to discuss a whitelisting arrangement.