If you attempt bursts, there is no guarantee that messages will be stored or displayed to users. Consult the method's documentation to better understand its rate limiting conditions. For example, chat.postMessage generally allows posting one message per second per channel, while also maintaining a workspace-wide limit. Rate limiting conditions are unique for methods with this tier.

Sporadic bursts are welcome.Įnjoy a large request quota for Tier 4 methods, including generous burst behavior. Tier 3 methods allow a larger number of requests and are typically attached to methods with paginating collections of conversations or users. Most methods allow at least 20 requests per minute, while allowing for occasional bursts of more requests. A small amount of burst behavior is tolerated. Feature/APIĪccess tier 1 methods infrequently. Overviewīroadly, you'll encounter limits like these, applied on a ' per API method per app per workspace' basis. This article gives an overview of the rate limits you're likely to encounter for Slack platform features, and then notes how the limits apply to each feature.

The details of how and when rate limiting works differs between features. Slack platform features and APIs rely on rate limits to help provide a predictably pleasant experience for users.

Slack api docs