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. one that is listed on the Slack App Directory) I would strongly recommend to put the production version of your App on a public webserver.The Slack API uses rate limits on a per-method and per-workspace basis. However for running a public Slack app (e.g. For developing and testing this is actually the better alternative, since you can test and fix your Slack app locally without having to deploy every change on a public server.
WAMP for windows) and open it to the Internet through a secure tunnel (e.g. Interactive Buttons)Īnother option is to run a webserver on your local machine (e.g. Also many other features of Slack requires you to run SSL on your webserver (e.g. The redirect URL works without SSL, but for security reasons SSL is strongly recommended. See also this answer on how the OAUTH process can be implemented. So the redirect URL is the URL to your installation script.īasically any webserver or script hosting service that runs your favorite script flavor (e.g. As already mentioned in the comments you will need a publicly reachable webserver to host your script for installing the Slack app.
0 kommentar(er)
