DeprecationDeskforced-migration deadlines

Slack

Slack Web API rejects GET and HEAD requests that carry a body on February 17, 2027

90 days left — Feb 17, 2027

What stops working
From February 17, 2027 any Slack Web API call made with HTTP GET or HEAD that includes a request body is rejected with an HTTP 403 error. Most affected apps do this by accident: HTTP libraries such as axios, Guzzle, Python requests and aiohttp add a body (often an empty {}) when a data or json option is set. POST calls and GET calls without a body keep working.
Who is affected
Every Slack app, bot or internal script that calls the Web API with GET and passes arguments or the token through a body option, including Slack CLI users on versions before v4.12.0.
Official migration path
Move all GET arguments into the query string, send the token in the Authorization: Bearer header, upgrade the Slack CLI to v4.12.0 or later, or switch the call to POST.
What the official path does not cover
Slack gives no tool to find the offending calls. Each integration's HTTP client configuration has to be audited, patched, redeployed and tested before the date; agencies that maintain many customer bots repeat this per codebase.
Source
Slack Developer Changelog: Web API GET and HEAD requests with a body will return 403 errors (Nov 16, 2026) · announced 2026-11-16 · verified 2026-11-18

Need this done before Feb 17, 2027?

Fixed price, fixed scope, fixed date. From $2,500 for a single integration or workflow; you get the working replacement, the code, and a before/after check. Quote within one business day.

Get a fixed-price quote →

One short form (company, email, what runs on this, needed-by). Reply within one business day.

Not ready yet? Get an email when Slack deadlines approach · Firms: get listed for Slack work.

Spotted a wrong date? Report it — corrected with the source within one business day.

← All deadlines