Some data (like user and channel information) doesn’t change often, so you may be able to cache some of it. Your first step should be to limit the number of API calls your app makes.

Rate limits are nothing to fear, but they can lead to a bad user experience if they’re not expected and handled within your app. When you’re developing an app, you should make sure the rate limits are what you expect so you can handle them accordingly - but how? Handling rate limits The full breakdown of the different Web API tiers and which each method belongs is on the API site. There are four tiers of rate limits on the platform that are purposefully vague and, in most cases, apps will stay well under the limits without even trying. For example, an app can call files.upload about 20 times a minute but can call chat.postEphemeral about 100 times a minute. The platform has a tiered rate limiting system: the number of times an app can call a method depends on the method. You also only need to worry about rate limiting for the Web API (the Events API has it too, but it’s 30,000 event deliveries per hour per workspace, so it’s unlikely you’ll hit a limit there).

And if your app is rate limited in one workspace, you can still make requests for other ones. In other words, if your app is rate limited for calling emoji.list too much, your token will still be able to call chat.postMessage. The Slack API uses rate limits on a per-method and per-workspace basis.

Slack api