Slack APIConnect Slack without building on its API
Slack has a public web API. Self-serve for any developer who creates a Slack app; the app must be installed to a workspace to get tokens. If you're reading the docs because you need Slack to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Slack and your other tools.
- APIWeb API (JSON)
- AuthOAuth 2.0
- AccessSelf-serve
What the Slack API gives you
- Type
- Web API (JSON)
- Authentication
- OAuth 2.0 (bot and user bearer tokens)
- Who can get access
- Self-serve for any developer who creates a Slack app; the app must be installed to a workspace to get tokens.
- What it covers
- 200+ methods covering messages, conversations/channels, users, files, reactions, and workspace info.
- Limits
- Per-method, per-workspace tiers run from Tier 1 (1+/min) to Tier 4 (100+/min); since May 29, 2025, new commercial apps not approved for the Marketplace are capped at 1 request/min and 15 objects per call on conversations.history and conversations.replies.
Official docs: docs.slack.dev. Checked September 2026. Vendors change access terms, so confirm with Slack before you build.
Building on the Slack API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Slack credentials, and manage tokens and refreshes. | Connect your Slack account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Slack task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Slack work off someone's desk, the build is the slow part.
What teams usually want the Slack API for
Client Document Batch Uploads
Caddi batch-uploads client documents to the correct matters, applies the right metadata and disclosures, and shares eligible files with clients — with a Slack notification when each batch is done.
Approval flow
Caddi posts an approval request to the right Slack channel, captures the response, and writes the decision back to the source system.
Critical-event notify
When a high-priority event lands in email or the CRM, Caddi posts to the relevant Slack channel with full context.
Daily ops digest
Each morning, Caddi posts the day's open work — overdue tasks, missing docs, aging invoices — to the right Slack channels.
Slack API questions
Does Slack have an API?
Yes. Slack has a public web API, authenticated with OAuth 2.0 (bot and user bearer tokens). The official documentation is at https://docs.slack.dev/apis/web-api/.
How do I get access to the Slack API?
Self-serve for any developer who creates a Slack app; the app must be installed to a workspace to get tokens.
Does the Slack API have rate limits?
Per-method, per-workspace tiers run from Tier 1 (1+/min) to Tier 4 (100+/min); since May 29, 2025, new commercial apps not approved for the Marketplace are capped at 1 request/min and 15 objects per call on conversations.history and conversations.replies.
Can I connect Slack to my other tools without writing code against its API?
Yes. With Caddi you show the Slack task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Slack and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Slack with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Slack is reviewed before it runs in production, and every run is logged.
Connect Slack without the build.
Drop your work email and pick a time. We'll show you Caddi running your Slack workflow end to end.