Slack API Error Code Ratelimited: How to Fix It

Q: What are Slack's API rate limits?

Slack rate limits vary by API method. Most methods allow 1-20 requests per minute per app per workspace. Some high-frequency endpoints like conversations.history allow up to 100 requests per minute. Check the specific documentation for each endpoint you're using.

Q: How long should I wait when rate limited?

Always use the Retry-After header value from the API response. This tells you the exact number of seconds to wait. If no header is present, start with 60 seconds and use exponential backoff for subsequent rate limits.

Q: Can I increase my Slack API rate limits?

Rate limits are generally fixed per API method and cannot be increased on request. However, enterprise customers may have access to higher limits. The best approach is to optimize your code to work within the existing limits.

Q: Why do I keep getting rate limited even with delays?

This usually happens when multiple instances of your app are running, when you're not respecting the Retry-After header, or when your delays are too short. Ensure you're implementing proper exponential backoff and not making concurrent requests that exceed limits.

Q: Does rate limiting affect all API methods equally?

No, different Slack API methods have different rate limits. Tier 1 methods (like auth.test) allow more requests than Tier 3 methods (like files.upload). Check the API documentation for specific limits on each endpoint you're using.

Abstract

The Slack 'ratelimited' error occurs when your application or bot exceeds the API rate limits set by Slack. This means you're making too many requests in a short time period, and Slack is temporarily blocking additional requests to protect their servers from overload.