Adjust a Slack app for the May 2025 conversations.history/conversations.replies rate-limit reduction
domain: docs.slack.dev · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Read the official changelog entry dated May 29, 2025 (clarified June 3, 2025) at docs.slack.dev/changelog/2025/05/29/rate-limit-changes-for-non-marketplace-apps
Determine whether your app is a Slack Marketplace app or an internal/non-Marketplace app — only non-Marketplace apps are affected
For affected apps created after May 29, 2025 (or new installs of existing non-Marketplace apps), plan for conversations.history and conversations.replies being limited to Tier 1 (roughly 1 request/minute)
Reduce the requested limit parameter on these calls to the new max/default of 15 objects per request and add pagination/backoff logic accordingly
If message-history throughput is business-critical, evaluate applying for Slack Marketplace distribution to retain the higher legacy rate limits (50+ requests/min, 1,000 objects)
Known gotchas
This is not a blanket Slack-wide rate-limit cut — it applies specifically to conversations.history and conversations.replies for non-Marketplace apps
Existing apps/installs created before May 29, 2025 may be grandfathered — verify your app's actual observed limits rather than assuming the new tier applies retroactively
Don't confuse this with the separate, unrelated "classic apps deprecation" timeline change Slack announced in December 2025 — they are different initiatives
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?