Web API GET and HEAD requests with a body will return 403 errors
On February 17th, 2027, the Web API will start rejecting HTTP GET and HEAD requests that include a request body. These requests will fail with an HTTP 403 error. This change is part of infrastructure updates to how API traffic reaches Slack.
Requests without a body aren't affected, and neither are POST requests.
Check whether your app is affected
Most affected apps 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. Your app is likely affected if it does any of the following when calling a Web API method with GET:
- passes
datain axios - passes
jsonorform_paramsin Guzzle - passes
data=orjson=in Pythonrequestsoraiohttp - puts method arguments in a form-encoded body instead of the query string
Update your app
For most apps, the fix is to stop sending a body with GET requests:
- Send
GETarguments in the query string, for exampleGET /api/conversations.history?channel=C123&limit=100. - Send your token in the
Authorization: Bearerheader, not in the body or the URL. - If you use
slack apifrom the Slack CLI, upgrade to v4.12.0 or later withslack upgradeand passGETarguments askey=valueinstead of--json. - Or use
POST, which supports both URL-encoded and JSON-encoded bodies.
If your arguments already go in the query string and your token in the Authorization header, dropping the body is the only change you need to make.