Skip to content

Ratelimiting

CoolProGamer edited this page Feb 27, 2025 · 2 revisions

Rate Limits

Rate limits exist across Decatur Robotics' APIs to prevent spam, abuse, and service overload. Limits are applied to individual bots and users both on a per-route basis and globally. Individuals are determined using a request's authentication—for example, a bot token for a bot.

Per route rate limits exist for many individual endpoints, and may include the HTTP method(GET,POST,PUT, or DELETE). In some cases, per-route limits will be shared across a set of similar endpoints, indicated in the X-RateLimit-Bucket header. It's recommended to use this header as a unique identifier for a rate limit, which will allow you to group shared limits as you encounter them.

During calculation, per-route rate limits often account for top-level resources within the path using an identifier—for example, guild_id when calling /guilds/{guild.id}/channels. Top-level resources are currently limited to channels(channel_id), guilds(guild_id)

Clone this wiki locally