Web API GET and HEAD requests with a body will return 403 errors
Slack announced that on February 17, 2027, the Web API will start returning an HTTP 403 error for GET and HEAD requests that include a request body. Requests without a body still work, and POST requests aren't affected.
Most apps that hit this don't send a body on purpose. Many HTTP libraries add a small body, often an empty {}, to a GET request when a body option is set. Slack lists these as likely causes:
- Passing data in axios
- Passing json or form_params in Guzzle
- Passing data= or json= in Python requests or aiohttp
- Putting method arguments in a form-encoded body instead of the query string
For most apps, the fix is to stop sending a body on GET calls. Put the arguments in the query string, for example GET /api/conversations.history?channel=C123&limit=100, and send your token in the Authorization: Bearer header rather than in the body or the URL. If you call the API through slack api in the Slack CLI, upgrade to v4.12.0 or later with slack upgrade and pass GET arguments as key=value instead of --json. Or switch the call to POST, which accepts both URL-encoded and JSON bodies.
If your arguments already go in the query string and your token is in the header, removing the body is the only change you need.