The limit is currently set at 10,000 per 10 minutes. If a single IP address makes too many invalid HTTP requests from the browser, they're restricted from accessing the Discord API. "message" : "You are being rate limited." , Your application must inspect the X-RateLimit-Reset-After header or retry_after from the body to check how long it needs to wait to retry the request.Īn example response from a request being rate limited will look like the following: < HTTP/1.1 429 TOO MANY REQUESTS
Smalland discord code#
What Happens When Rate Limits Are Exceeded?ĭiscord will return a 429 status code after reaching a rate limit. It's a unique string, representing that the user has gotten rate-limited for their Discord channel. This random string doesn't mean anything, but it keeps track of this Discord rate limit. The last thing here is X-RateLimit-Bucket,which is a random string given by Discord. The X-RateLimit-Reset-After gives the time in seconds before our rate limit will be reset.
Smalland discord software#
Many computer systems and software use this time, which can be easily converted into a human-readable format. If you haven't heard of it, Epoch time is the universal Unix time, which is the time elapsed since Jan 1, 1970.
X-RateLimit-Reset gives the Epoch time when the rate limit will be reset. The X-RateLimit-Remaining means the remaining requests available during the bucket time window before the limit is reset. Here, X-RateLimit-Limit means the total number of requests we can make to this endpoint. Now let's understand what these terms mean. The response header will look like this: X-RateLimit-Limit: 30 Generally, developers hit this rate limit when their community grows and their Discord bots need to process more requests. The rate limits are always given on the response headers, which can be found in the developer tools section of your browser. On top of that, Discord also has a global limit of fifty requests per second. What Are Rate Limits?ĭiscord has different rate limits for routes and discord bots. The first method is synchronization with Redis, and the second method uses a global request proxy. We will explore in detail two methods to solve the rate limit issue. In this post, we'll look into dealing with Discord API rate limiting from a developer's perspective. But sometimes, this becomes an issue for a genuine person who's developing a product using these APIs. It can also be applied to user types, e.g., paying users usually have higher limits than free users. The rate limit's there so that hackers or bots don't abuse it, because if they send too many requests quickly, it could break the API endpoint. Most freely available APIs and commercial APIs have a rate limit.
0 kommentar(er)
