Slack APIBreaking changehigh

Slack rejects GET and HEAD requests with a body starting Feb 17, 2027

Detected
Nov 17, 2026
Effective
Feb 17, 2027(in 92 days)
Confidence
97%

What changed

On February 17, 2027, Slack's Web API will reject HTTP GET and HEAD requests that include a request body with a 403 error. Many HTTP libraries silently attach a body to GET requests, so apps using axios, Guzzle, Python requests, or aiohttp may be affected without realizing it.

What to do

Move all GET request parameters to the query string, send tokens via the Authorization: Bearer header, and ensure no request body is attached to GET/HEAD calls. Alternatively, switch to POST requests. If using Slack CLI, upgrade to v4.12.0+.

Affected

endpoint: * (all Web API GET endpoints)endpoint: * (all Web API HEAD endpoints)header: Authorization

Source: api.slack.com (Slack's own page, checked by Breakwatch)

Is your code affected?

Search your repositories for the Slack SDK and the names above:

npm: @slack/web-apinpm: @slack/boltpip: slack_sdkruby: slack-ruby-clientgo: github.com/slack-go/slackphp: jolicode/slack-php-apijava: com.slack.api:slack-api-client

Or let Breakwatch do it: connect a repo and see which files call Slack, then get the next change as an alert pointing at those files. Check a repo free

Put it in your calendar: Slack deadlines (.ics) or every vendor's.

Get Slack API changes by email

Once a week: the breaking changes and upcoming deadlines for Slack, each linked to the vendor's own page. Free, no account. One-click unsubscribe.

More Slack API changes

Every Slack API change →