What Discord changed, 24 April 2026 to 29 October 2026
231 operations became 250. None were removed, 0 were newly deprecated, 19 were added, and 0 request fields became required.
Read from discord/discord-api-spec at 493dc48 and 4e75626 (version 10). Generated 31 October 2026 by the specification parser the APIBreak Action uses, applied to Discord's published specification.
Discord publishes its HTTP API description in discord/discord-api-spec. This page reads specs/openapi.json, not specs/openapi_preview.json. Version policy and shutdown dates are not in the specification, so this page does not state them; it reads the deprecated flag on each operation.
Removed from the specification
Nothing was removed in this window. That is a real result, not a gap in the check.
Newly deprecated in this window
A deprecation is the notice period. It is the cheapest moment to act and the easiest one to miss. This list compares operations present at the baseline.
No compared operation (one paired with a baseline operation) gained the deprecated flag in this window.
Deprecated as of the current specification (0)
Everything the vendor currently marks deprecated, whether or not it changed recently. The vendor has flagged each of these for possible removal, with or without a date attached.
No operation is currently marked deprecated.
Request fields removed from the specification
The current specification no longer lists these request fields, which the baseline did. A caller that still sends one is sending a parameter the new version does not define; whether Discord rejects or ignores it at runtime is not something a specification diff can show, and what it means for an integration depends on how Discord versions — see the note at the top of this page.
- PATCH /channels/{channel_id}/messages/{message_id} no longer lists attachments[].is_remix (application/json)
- PATCH /channels/{channel_id}/messages/{message_id} no longer lists attachments[].is_remix (application/x-www-form-urlencoded)
- PATCH /channels/{channel_id}/messages/{message_id} no longer lists attachments[].is_remix (multipart/form-data)
- PATCH /webhooks/{webhook_id}/{webhook_token}/messages/{message_id} no longer lists attachments[].is_remix (application/json)
- PATCH /webhooks/{webhook_id}/{webhook_token}/messages/{message_id} no longer lists attachments[].is_remix (application/x-www-form-urlencoded)
- PATCH /webhooks/{webhook_id}/{webhook_token}/messages/{message_id} no longer lists attachments[].is_remix (multipart/form-data)
- PATCH /webhooks/{webhook_id}/{webhook_token}/messages/@original no longer lists attachments[].is_remix (application/json)
- PATCH /webhooks/{webhook_id}/{webhook_token}/messages/@original no longer lists attachments[].is_remix (application/x-www-form-urlencoded)
- PATCH /webhooks/{webhook_id}/{webhook_token}/messages/@original no longer lists attachments[].is_remix (multipart/form-data)
- POST /channels/{channel_id}/messages no longer lists attachments[].is_remix (application/json)
- POST /channels/{channel_id}/messages no longer lists attachments[].is_remix (application/x-www-form-urlencoded)
- POST /channels/{channel_id}/messages no longer lists attachments[].is_remix (multipart/form-data)
- POST /lobbies/{lobby_id}/messages no longer lists attachments[].is_remix (application/json)
- POST /lobbies/{lobby_id}/messages no longer lists attachments[].is_remix (application/x-www-form-urlencoded)
- POST /lobbies/{lobby_id}/messages no longer lists attachments[].is_remix (multipart/form-data)
Discord API questions
Every answer below is computed from the snapshot above, and each links to the Discord specification it was read from.
- Which Discord API endpoints were removed recently?
- None between 24 April 2026 and 29 October 2026, in specs/openapi.json in discord/discord-api-spec. It went from 231 to 250 operations in that window, and every operation present at the start was still there at the end, at the same URL.
- Source: discord/discord-api-spec, the two commits compared
- Which Discord API endpoints are deprecated?
- No operation in specs/openapi.json in discord/discord-api-spec, as of 29 October 2026, carries the deprecated flag. A specification can only show a deprecation the vendor marks in it, so Discord's own changelog may still announce one.
- Source: discord/discord-api-spec, the two commits compared
- Did any Discord API request fields become required?
- None between 24 April 2026 and 29 October 2026, among the JSON request bodies in specs/openapi.json in discord/discord-api-spec the comparison could read. A field inside a union (anyOf or oneOf) is not compared, so it is not counted either way.
- Source: discord/discord-api-spec, the two commits compared
- Where is the Discord OpenAPI specification?
- In the discord/discord-api-spec repository on GitHub. This page reads specs/openapi.json at commit 4e75626 (version 10), dated 29 October 2026.
- Source: discord/discord-api-spec on GitHub
The Action does not check Discord yet
It checks GitHub REST and Stripe. If you want your CI to check the Discord endpoints you call, say so in an issue, because requests like that decide which vendor the Action should support next.