Monitor Slack API deprecations, bot scope changes, and event updates
Keep your Slack integrations working as the platform API evolves
APIDrift monitors Slack's API changelog for Web API deprecations, Events API changes, Block Kit updates, and bot token scope modifications that affect your Slack apps and integrations.
No credit card. Slack is pre-configured. Get your first digest this week.
3
Sources tracked
HTML scraping
Source type
standard
Content depth
Slack aggressively deprecates API methods — your bot can stop working overnight
Slack regularly removes API methods, changes OAuth scopes, and updates Block Kit components. Their migration timelines can be aggressive, and a deprecated method will start returning errors with little warning. If your Slack bot is critical to your team's workflow, you need advance notice.
“Slack deprecated conversations.list with the legacy bot token scope. Our standup bot that listed channels just stopped working one Monday morning. The 400 users who relied on it were not happy.”
Manual monitoring vs APIDrift
Without APIDrift
Check frequency
When you remember
Change classification
Read every line yourself
Alert timing
Days or weeks late
Team visibility
Tribal knowledge
Setup time
Bookmarks, RSS, custom scripts
With APIDrift
Check frequency
Every 6 hours, automatically
Change classification
AI-powered severity & type tagging
Alert timing
Same-day smart digests
Team visibility
Shared watchlist & history
Setup time
One click, 30 seconds
What APIDrift tracks for Slack
Web API method changes
Deprecated methods, new required parameters, and response schema modifications
Events API updates
New event types, payload changes, and subscription behavior modifications
Block Kit changes
New block types, deprecated elements, and interaction payload modifications
How it works
Add Slack to your watchlist
One click. No config needed.
We scrape & diff every 6 hours
AI classifies each change by type and severity.
Get smart digests
Email, Slack, or webhook — your choice.
Example: What an alert looks like
Web API: channels.* methods fully removed — use conversations.* methods
All legacy channels.* methods now return method_deprecated errors. Migrate to the corresponding conversations.* methods. The conversations API requires different OAuth scopes.
Events API: reaction_added payload removing item.channel field — use channel at top level
The nested item.channel field in reaction_added events is deprecated. Use the top-level channel field instead. The nested field will be removed in 6 months.
This is a static preview — not live data.
Frequently asked questions
Start monitoring Slack today
Stop checking changelogs manually.
Free plan. No credit card. 30-second setup.