← All monitored APIs
Discord // api changelog

Discord API changelog

We check Discord's changelog and OpenAPI spec every day, because we run production integrations on the Discord API. This page lists the 114 changes we have recorded since monitoring started on 26 March 2026, newest first.

Our last successful check was on 6 October 2026. We are on it; until then this page may miss the newest changes.

In short

6 breaking changes and 1 deprecation in the Discord API in the last 90 days. The latest: “Custom Status Hidden by Profile Privacy Settings” (17 September 2026).

Latest detection, 8 October 2026 Discord removed the `MediaGalleryItemRequest` schema; update generated clients or request models that reference it. Responses across message, pin, thread, poll, interaction-callback, and webhook endpoints now include optional `actor` fields on messages and referenced messages; no action is needed unless response parsing is strict.

6 Breaking, 90 days
1 Deprecations, 90 days
114 Changes on record
Last checked

Discord API changes

Labels are assigned automatically. Check the vendor's note before planning work around an entry.

September 2026

  1. Age Assurance

    What It Means for Discord Developers: Age assurance protections now limit visibility of custom statuses from user presence for private profiles and may filter DMs to Message Requests, affecting bots and apps receiving presence data.

  2. New Invite Target User Endpoints and Options

    Added four new endpoints for managing invite target users individually (add, remove, bulk-add, bulk-delete) instead of requiring CSV file uploads.

  3. Custom Status Hidden by Profile Privacy Settings

    Custom status activities are now omitted from presence updates when users have restrictive privacy settings, affecting bots subscribed to guild presence.

  4. Unlinking Accounts Guide

    New documentation guide published for best practices on unlinking Discord accounts, including handling APPLICATION_DEAUTHORIZED webhook events.

  5. Shard Param Required for Get Current User Guilds with Large Bot Sharding

    Apps using large bot sharding must now pass the `shard` query parameter to Get Current User Guilds endpoint; requests without it return 400 Bad Request.

    Affects one of your integrations? We take over the migration, at a fixed price
  6. Slash Command Improvements and Mobile Fixes

    Added multiline input support for string options, fuzzy search in autocomplete, and fixed multiple mobile bugs with slash commands.

  7. Default File Upload Limit Increase

    Default file upload limit increased from 10 MiB to 20 MiB for all users, bots, webhooks, and interaction responses.

  8. Discord Social SDK Release 1.10.19337 - Voice Settings

    Added read-only access to Discord desktop client's voice settings including mute/deafen state, volumes, and push-to-talk key via new VoiceSettings class.

August 2026

  1. PRUNE_REQUIRES_ADMIN Guild Feature

    Get Guild Prune Count and Begin Guild Prune endpoints now require ADMINISTRATOR permission if guild has the PRUNE_REQUIRES_ADMIN feature enabled.

  2. Account Linking on Web

    New guide published for account linking using standard OAuth2 web flow; removed partner-only restriction for enabling Discord entry points.

  3. Game Stats Widgets

    New feature allowing games to configure widgets displaying player stats (rank, playtime, wins, custom metrics) on Discord profiles via Application Identity Profile.

  4. Deprecation

    Battle.net Connections in Get Current User Connections: Newly created Battle.net connections no longer returned by Get Current User Connections endpoint; existing ones removed starting September 22, 2026.

  5. Discord Social SDK Release 1.10.18687 - iOS OAuth Fix

    Fixed iOS web-authentication session override issue that could interfere with host app's ASWebAuthenticationSession delegate during OAuth flow.

  6. Channel Obfuscation for Users and Bots

    Bots can no longer see channels they lack VIEW_CHANNEL permission for; obfuscated channels show hidden name and nulled sensitive fields over Gateway; HTTP endpoint omits them entirely starting November 16, 2026.

    Affects one of your integrations? We take over the migration, at a fixed price
  7. Discord Social SDK Hotfix Releases 1.10.18369, 1.9.18337 & 1.8.18335

    Fixed incorrect bool marshaling across C#/native boundary and crash from iterator invalidation in lobby callbacks on PlayStation 5.

  8. Channel application_id is Now Nullable

    The channel object's application_id field is now nullable for future guild channels; apps must handle null values.

  9. Filter File Types in File Uploads and Attachment Options

    Added ability to restrict file types in File Upload components and ATTACHMENT command options for improved security.

July 2026

  1. Discord Social SDK Release 1.10.18247

    Updated console OS support requirements, added Xbox presence reading, Android rich presence via RPC, macOS framework changes, and WebRTC M130 update.

    Affects one of your integrations? We take over the migration, at a fixed price
  2. Provisional Accounts Documentation Restructure

    Provisional accounts documentation reorganized into dedicated section with separate pages for each flow and implementation path.

  3. Resolved Channel app_permissions in Interactions

    Resolved channel objects in interaction payloads now include app_permissions field showing bot's permissions in that channel.

  4. Deprecation

    Riot Games Connections in Get Current User Connections: Newly created Riot Games connections no longer returned by Get Current User Connections endpoint; legacy connections stop being returned July 10, 2026.

June 2026

  1. Discord Social SDK Release 1.9.17379

    Fixed crash caused by re-entrant HTTP requests during connection teardown on PlayStation 5.

  2. Discord Social SDK Release 1.9.17228 - Krisp Integration

    Fixed AUTHORIZE_REQUEST event resubscription issue and integrated Krisp noise suppression binaries in Unity and Unreal packages.

  3. Attachment Editing and is_spoiler Param

    Apps can now edit attachment description and is_spoiler parameters when editing messages; attachments can be marked as spoilers via flag.

  4. Documentation Fix

    Subscription Status Values: Corrected documentation where INACTIVE (1) and ENDING (2) subscription status integer values were previously swapped; API was always correct.

  5. Changes to Privileged Intent Access for Discord Apps

    Privileged intent threshold changed from server-based (100+) to user-based (10,000+); apps must now reapply annually for access.

  6. Discord Social SDK Release 1.9.16441

    Fixed crash caused by use-after-free in WebSocket callbacks on PlayStation 5.

  7. New Lobby HTTP API Endpoints

    Added public endpoints for Create/Join Lobby, Send/Get Lobby Messages, and Create Lobby Channel Invites.

May 2026

  1. Discord Social SDK Release Cadence & Support

    New three-per-year release schedule (April, July, November) with support window covering five most recent minor versions.

  2. Account Linking Failure Modes Documentation

    Expanded documentation covering Discord account bans, explicit unmerges, and OAuth2 token revocation scenarios for account linking.

  3. Discord Social SDK Release 1.9.15780

    Added Xbox GDK 260400 support and integrated Krisp noise suppression across Android, iOS, macOS, and Windows.

  4. New flags_new Field on Application Object

    Added flags_new field to Application object containing full set of application flag bits as string-serialized integer for flags beyond bit 30.

  5. User Premium Type Field Now Requires A Scope

    premium_type field returns 0 unless application has been approved for identify.premium scope; scope is only available to approved partners.

April 2026

  1. Voice Muting Based on Player Blocks

    New guide for implementing bi-directional voice muting in lobby calls; documents POST /lobbies/{lobby.id}/members/bulk endpoint for bulk member operations.

  2. Voice Muting Based on Player Blocks

    New guide published on implementing bi-directional voice muting in lobby calls based on block relationships; documented bulk member update endpoint.

  3. Activity Invites Attribution Fix

    Fixed bug where activity invites from sibling applications were sometimes attributed to wrong app; now uses application_id from invite when provided.

  4. Discord Social SDK Release 1.9.15332

    Added PlayStation 5 OS 13.000 support and fixed activity invite attribution for sibling applications using Publisher Level Account Linking.

  5. Proximity Voice Chat Guide for Game Developers

    Published new guide on adding proximity voice chat to multiplayer games using Discord Social SDK and Unity.

  6. Security Updates for Provisional Account OIDC Integrations

    Enhanced OIDC validation with stricter hostname checks and HTTP redirect blocking; existing integrations unaffected but new configurations must meet updated requirements.

  7. Voice Channel Status and Start Time Documentation

    Officially documented voice channel status endpoint, permission (SET_VOICE_CHANNEL_STATUS), Gateway events, and audit log events for voice channel status management.

  8. Deprecation

    OAuth2 Refresh Token Grant for OIDC Provisional Accounts: OAuth2 refresh_token grant for OIDC provisional accounts is deprecated; use Client::UpdateToken with fresh provider tokens instead.

  9. Message Forwarding Requires Message Content Access

    Applications must now have message content read access to forward messages; attempting to forward unreadable messages returns error 160014.

  10. Discord Social SDK Release 1.8.14985

    Added Xbox GDK 251002 support.

  11. RPC over IPC Documentation

    New documentation for Discord's RPC over IPC transport for native applications, covering socket paths, handshake flow, and IPC-specific events.

March 2026

  1. Discord Social SDK Release 1.8.14856

    Added debug plugin support for iOS Unity and Unreal packages and fixed party privacy propagation bug.

  2. Search Guild Messages

    New endpoint for bots to search messages within a guild by content, author, channel, mentions, attachments, and embeds.

  3. Discord Social SDK Release 1.8.14587

    Added Debug library support across multiple platforms including Unity, Unreal, Windows, Mac, Linux, Android, and consoles.

  4. Developer Portal & Docs Refresh

    Updated Developer Portal and Docs with improved navigation, new theme, localization support, reorganized structure, and AI/MCP support.

  5. Discord Social SDK Release 1.8.14437

    Enhanced security logging with bearer token filtering and severity level restrictions for debug vs release builds.

  6. Updates to Context Menu Commands

    UI for User and Message Commands redesigned for easier discovery and higher command limits.

February 2026

  1. Server-Side Message Moderation

    Released two new API endpoints for modifying application-scoped moderation metadata on game direct messages and lobby messages.

  2. Discord Social SDK Release 1.8.14026

    Fixed crash when linking Discord account to application while in a voice call.

  3. Publisher Level Account Linking

    New feature enabling game publishers with multiple titles to implement single authorization flow across entire game portfolio with centralized account management.

  4. Community Invite Guide

    New guide showcasing invite endpoints with examples for creating invites with roles and restricting access using target_users.

  5. Discord Social SDK Release 1.8.13870

    New SDK release with PlayStation 5 OS 12.000 support and iOS code stripping for size reduction.

  6. Radio Groups, Checkbox Groups, and Checkboxes in Modals

    Three new modal components added: Radio Groups for single-selection, Checkbox Groups for multi-selection, and Checkboxes for boolean toggles.

  7. Next Generation Docs Project

    Migrated Discord developer documentation to Mintlify platform with improved navigation, search, PR previews, AI/LLM support, and MCP server integration.

  8. Community Invites Update

    Breaking changes to community invite endpoints: Get Target Users now returns standardized CSV format, Get Channel Invites returns partial role objects instead of full objects.

January 2026

  1. Relationships.read scope for Activities

    relationships.read scope opened for Activities under Social SDK terms; no approval needed; getRelationships() now returns player relationships.

  2. New Invite Endpoints

    New endpoints for community invites supporting role assignment and user-targeted access restrictions via Create Channel Invite, Get Target Users, Update Target Users, and Get Target Users Job Status endpoints.

  3. New Invite Endpoints

    Added new invite endpoints and functionality allowing invites to grant roles and restrict acceptance to specified users via target_users_file and role_ids parameters.

  4. New Invite Endpoints for Role Assignment and User Targeting

    Added Create Channel Invite support for `target_users_file` and `role_ids` parameters, plus new endpoints: Get Target Users, Update Target Users, and Get Target Users Job Status.

December 2025

  1. Discord Social SDK Release 1.8.13395

    Added MessageHandle::ModerationMetadata support for moderation key-value pairs and WebSocket error reporting with HTTP status codes.

  2. Discord Social SDK Release 1.7.13357

    Fixed crash on Steam Deck and iOS in specific scenarios.

  3. New Social SDK Guide

    Account Linking from Discord: New guide showing how to enable account linking entry points within Discord client with Connected Game Flow and Web Flow implementation options.

  4. Discord Social SDK Release 1.6.13305

    Fixed crash on Steam Deck and iOS in specific scenarios.

  5. Get Guild Role Member Counts Endpoint

    New endpoint allowing apps to retrieve the number of members that have each role in a guild.

  6. Discord Social SDK Release 1.7.13152

    Added macOS 10.15 support for Intel Macs with minimum versions now 10.15 Intel and 11.0 Apple Silicon.

November 2025

  1. New BYPASS_SLOWMODE Permission & Permission Split

    New BYPASS_SLOWMODE permission (1 << 52) split from MANAGE_MESSAGES, MANAGE_CHANNEL, and MANAGE_THREADS; required February 23, 2026.

  2. Permission Changes Going into Effect February 2026

    Breaking changes effective February 23, 2026: PIN_MESSAGES, BYPASS_SLOWMODE, CREATE_GUILD_EXPRESSIONS, CREATE_EVENTS permissions split from original permissions; old permissions will no longer grant these abilities.

  3. Discord Social SDK Release 1.7.13024

    Windows default audio device selection fix to prefer system default instead of fallback.

  4. Guild Expressions and Events Permissions Now Available to Developers

    CREATE_GUILD_EXPRESSIONS and CREATE_EVENTS permissions now available for bots; will be required starting February 23, 2026 instead of MANAGE_GUILD_EXPRESSIONS and MANAGE_EVENTS.

  5. Discord Social SDK Release 1.7

    Added Sign in with Apple and PlayStation Network support; linked channels now sorted by Discord client order with additional properties.

  6. Discord Social SDK Release 1.7 - Major Features

    Added Apple Sign-in and PlayStation Network authentication, sorted guild channels by position, added Low Energy Mode support for PS5, upgraded WebRTC to m130, and improved voice reliability.

  7. Discord Social SDK Release 1.6.12767

    New SDK release with crash fix for PlayStation when creating, destroying, and recreating Discord client.

October 2025

  1. Discord Social SDK Release 1.5.12211

    New SDK release with crash fix for Client::GetUserGuilds on iOS devices.

  2. Discord Social SDK Release 1.6.12170

    New SDK release with custom invite banner images via activity.assets.inviteCoverImage, customizable app name via activity.name, Xbox GDK 2025.04 support, and iOS crash fix.

  3. File Upload Component in Modals

    New File Upload component added to modals enabling collection of files from users in addition to text.

September 2025

  1. Discord Social SDK 1.6 - Game Profile Integration and In-Discord Authentication

    SDK 1.6 adds Game Profile Integration for displaying game data on Discord profiles, In-Discord Authentication Flow support, channel position sorting, performance caching improvements, and critical voice and stability bug fixes.

  2. Discord Social SDK Release 1.6

    Major SDK release with channel sorting improvements, message notification suppression, game profile integration features, in-Discord authentication flow support, and GetCurrentUser API deprecation.

  3. Discord Social SDK Release 1.6

    Major SDK release with guild channels sorted by position, and additional GuildChannel properties (type, position, parent category ID).

  4. Adding More Modal Components

    User, Role, Mentionable, and Channel select menus now supported in modals within Label components; Text Display component with markdown support added.

  5. Banner, Avatar, and Bio on Modify Current Member

    Bots can now set banner, avatar, and bio fields using modify current member endpoint.

  6. Deprecating Non-E2EE Voice Calls

    Only E2EE calls will be supported starting March 1, 2026; all audio/video in DMs, GDMs, voice channels, and Go Live streams must use DAVE encryption or will disconnect.

August 2025

  1. Discord Social SDK Release 1.5.11353 - Android Crash Fixes

    Fixed crash on low-end Android devices in CreateOrJoinLobbyWithMetadata and when passing large metadata amounts.

  2. Introducing New Modal Components

    Added Label component for modals, String Selects now work in modals inside Label components, Text Inputs can be in Label components, and deprecated ActionRow + TextInput.

  3. New Modal Components - Label, String Select, Text Input

    New Label component for modals containing Text Inputs or String Selects; String Selects now work in modals with required field; ActionRow + TextInput deprecated.

  4. Pin Permission Split

    PIN_MESSAGES permission now split from MANAGE_MESSAGES; effective immediately but backwards compatible until January 12, 2026 when MANAGE_MESSAGES will no longer grant pin/unpin ability.

  5. Discord Social SDK Release 1.5 - DM History and Rich Presence

    Added DM history support with GetUserMessageSummaries and GetUserMessagesWithLimit, new activity types (Listening, Watching, Competing), cross-device invite acceptance, and linked channels guild joining.

February 2025

  1. New Modal Components - Radio Groups, Checkbox Groups, Checkboxes

    Three new modal components added: Radio Group for single selection, Checkbox Group for multi-selection, and Checkbox for boolean toggles.

November 2024

  1. New BYPASS_SLOWMODE Permission

    New BYPASS_SLOWMODE permission introduced to allow designated roles/users to bypass slowmode restrictions; effective February 23, 2026.

  2. Permission Changes Going into Effect February 2026

    PIN_MESSAGES, BYPASS_SLOWMODE, CREATE_GUILD_EXPRESSIONS, and CREATE_EVENTS permissions will no longer be granted by their parent permissions starting February 23, 2026.

  3. Guild Expressions and Events Permissions Now Available to Developers

    CREATE_GUILD_EXPRESSIONS and CREATE_EVENTS permissions now available to bot developers; will be required starting February 23, 2026.

  4. Discord Social SDK Release 1.7 - Authentication and Linked Channels

    Social SDK 1.7 adds Sign in with Apple and PlayStation Network support, improved channel sorting, and Low Energy Mode support for PS5.

October 2024

  1. File Upload Component in Modals

    New File Upload component added to modals supporting 0-10 files with configurable min/max requirements and any file type.

September 2024

  1. Discord Social SDK Release 1.6 - Game Profile and Authentication

    SDK 1.6 adds game profile integration on Discord user profiles, in-Discord authentication flow support, and multiple bug fixes and performance improvements.

  2. Banner, Avatar, and Bio on Modify Current Member

    Bots can now set banner, avatar, and bio fields using the modify current member route.

  3. New Modal Components - Select Menus and Text Display

    User, Role, Mentionable, and Channel Select menus now supported in modals; Text Display component added with markdown support.

  4. Deprecating Non-E2EE Voice Calls

    Only E2EE (DAVE) voice calls will be supported starting March 1, 2026; all clients and applications must update to support end-to-end encryption.

August 2024

  1. New Modal Components - Label and String Select

    New Label component added for modals with title and description; String Selects now work in modals when placed in Label component.

  2. Pin Permission Split

    PIN_MESSAGES permission split from MANAGE_MESSAGES; effective immediately but MANAGE_MESSAGES will stop granting this ability on January 12, 2026.

  3. Discord Social SDK Release 1.5 - DM History and Rich Presence

    SDK 1.5 adds DM chat history support, cross-device game invite acceptance, and new Rich Presence activity types.

April 2024

  1. Message Forwarding Requires Message Content Access

    Applications must now have message content read access to forward messages; attempting to forward without access returns error code 160014.

  2. RPC over IPC Documentation

    Documentation for Discord's RPC over IPC transport layer now available for native applications to communicate with local Discord client.

March 2024

  1. Search Guild Messages Endpoint Documentation

    New Search Guild Messages endpoint added for bots to search messages within guilds with filtering and sorting capabilities.

  2. Developer Portal & Docs Refresh

    Developer Portal and Documentation migrated to Mintlify with improved navigation, new localization support, and AI/MCP integration capabilities.

  3. Updates to Context Menu Commands UI

    Context menu commands UI redesigned with organization by application, frequently used hoisting, and search bar; limit increased from 5 to 15 per type.

February 2024

  1. Server-Side Message Moderation

    New API endpoints released for modifying application-scoped moderation metadata on game direct messages and lobby messages with webhook event support.

  2. Publisher Level Account Linking

    New documentation for Publisher Level Account Linking feature enabling game publishers to implement single authorization flow across multiple titles.

  3. Community Invite Guide

    New guide published showcasing invite endpoints functionality for creating invites with roles and restricting access to specific users.

  4. Radio Groups, Checkbox Groups, and Checkboxes in Modals

    Three new modal components added: Radio Group for single selection, Checkbox Group for multi-selection, and Checkbox for boolean toggles.

  5. Community Invites Update - Breaking Change

    Get Target Users endpoint now returns standardized CSV with only 'user_id' header; Get Channel Invites now returns partial role objects instead of full role objects.

January 2024

  1. Relationships.read Scope for Activities

    Relationships.read scope opened for Activities; no longer requires Discord approval, getRelationships() now available in Embedded App SDK.

  2. New Invite Endpoints

    New invite endpoints added to grant roles and restrict access to specified users; includes target_users_file and role_ids parameters.

OpenAPI spec changes

Differences between consecutive versions of Discord's published OpenAPI spec, as reported by oasdiff. Only changes that break or may break existing clients are listed.

  1. 30 potentially breaking
    • Potentially breaking POST /channels/{channel_id}/messages removed the request property '/allOf[#/components/schemas/MessageCreateRequest]/attachments/items/is_remix' (media type: multipart/form-data)
    • Potentially breaking POST /channels/{channel_id}/messages removed the request property 'attachments/items/is_remix' (media type: application/x-www-form-urlencoded)
    • Potentially breaking POST /channels/{channel_id}/messages removed the request property 'attachments/items/is_remix' (media type: application/json)
    • Potentially breaking PATCH /channels/{channel_id}/messages/{message_id} removed the request property '/allOf[#/components/schemas/MessageEditRequestPartial]/attachments/items/is_remix' (media type: multipart/form-data)
    • Potentially breaking PATCH /channels/{channel_id}/messages/{message_id} removed the request property 'attachments/items/is_remix' (media type: application/json)
    • Potentially breaking PATCH /channels/{channel_id}/messages/{message_id} removed the request property 'attachments/items/is_remix' (media type: application/x-www-form-urlencoded)
    • Potentially breaking POST /channels/{channel_id}/threads removed the request property '/anyOf[#/components/schemas/CreateForumThreadRequest]/message/attachments/items/is_remix' (media type: application/json)
    • Potentially breaking POST /channels/{channel_id}/threads removed the request property '/anyOf[#/components/schemas/CreateForumThreadRequest]/message/attachments/items/is_remix' (media type: application/x-www-form-urlencoded)
    • Potentially breaking POST /channels/{channel_id}/threads removed the request property '/anyOf[#/components/schemas/CreateForumThreadRequest]/message/attachments/items/is_remix' (media type: multipart/form-data)
    • Potentially breaking POST /interactions/{interaction_id}/{interaction_token}/callback removed the request property '/anyOf[#/components/schemas/CreateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookInteractionRequest]/attachments/items/is_remix' (media type: application/json)
    • Potentially breaking POST /interactions/{interaction_id}/{interaction_token}/callback removed the request property '/anyOf[#/components/schemas/CreateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookInteractionRequest]/attachments/items/is_remix' (media type: multipart/form-data)
    • Potentially breaking POST /interactions/{interaction_id}/{interaction_token}/callback removed the request property '/anyOf[#/components/schemas/CreateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookInteractionRequest]/attachments/items/is_remix' (media type: application/x-www-form-urlencoded)
    • Potentially breaking POST /interactions/{interaction_id}/{interaction_token}/callback removed the request property '/anyOf[#/components/schemas/UpdateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookUpdateForInteractionCallbackRequestPartial]/attachments/items/is_remix' (media type: application/json)
    • Potentially breaking POST /interactions/{interaction_id}/{interaction_token}/callback removed the request property '/anyOf[#/components/schemas/UpdateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookUpdateForInteractionCallbackRequestPartial]/attachments/items/is_remix' (media type: multipart/form-data)
    • Potentially breaking POST /interactions/{interaction_id}/{interaction_token}/callback removed the request property '/anyOf[#/components/schemas/UpdateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookUpdateForInteractionCallbackRequestPartial]/attachments/items/is_remix' (media type: application/x-www-form-urlencoded)
    • Potentially breaking POST /lobbies/{lobby_id}/messages removed the request property 'attachments/items/is_remix' (media type: application/json)
    • Potentially breaking POST /lobbies/{lobby_id}/messages removed the request property 'attachments/items/is_remix' (media type: multipart/form-data)
    • Potentially breaking POST /lobbies/{lobby_id}/messages removed the request property 'attachments/items/is_remix' (media type: application/x-www-form-urlencoded)
    • Potentially breaking POST /webhooks/{webhook_id}/{webhook_token} removed the request property '/anyOf[#/components/schemas/IncomingWebhookRequestPartial]/attachments/items/is_remix' (media type: application/json)
    • Potentially breaking POST /webhooks/{webhook_id}/{webhook_token} removed the request property '/anyOf[#/components/schemas/IncomingWebhookRequestPartial]/attachments/items/is_remix' (media type: application/x-www-form-urlencoded)
    • Potentially breaking POST /webhooks/{webhook_id}/{webhook_token} removed the request property '/anyOf[#/components/schemas/IncomingWebhookRequestPartial]/attachments/items/is_remix' (media type: multipart/form-data)
    • Potentially breaking POST /webhooks/{webhook_id}/{webhook_token} removed the request property '/anyOf[#/components/schemas/IncomingWebhookUpdateRequestPartial]/attachments/items/is_remix' (media type: multipart/form-data)
    • Potentially breaking POST /webhooks/{webhook_id}/{webhook_token} removed the request property '/anyOf[#/components/schemas/IncomingWebhookUpdateRequestPartial]/attachments/items/is_remix' (media type: application/json)
    • Potentially breaking POST /webhooks/{webhook_id}/{webhook_token} removed the request property '/anyOf[#/components/schemas/IncomingWebhookUpdateRequestPartial]/attachments/items/is_remix' (media type: application/x-www-form-urlencoded)
    • Potentially breaking PATCH /webhooks/{webhook_id}/{webhook_token}/messages/@original removed the request property '/allOf[#/components/schemas/IncomingWebhookUpdateRequestPartial]/attachments/items/is_remix' (media type: multipart/form-data)
    • and 5 more
  2. 5 potentially breaking
    • Potentially breaking GET /channels/{channel_id}/invites removed the optional property '/items/oneOf[#/components/schemas/GuildInviteResponse]/liveliness' from the response with the '200' status
    • Potentially breaking POST /channels/{channel_id}/invites removed the optional property '/oneOf[#/components/schemas/GuildInviteResponse]/liveliness' from the response with the '200' status
    • Potentially breaking GET /guilds/{guild_id}/invites removed the optional property '/items/oneOf[#/components/schemas/GuildInviteResponse]/liveliness' from the response with the '200' status
    • Potentially breaking DELETE /invites/{code} removed the optional property '/oneOf[#/components/schemas/GuildInviteResponse]/liveliness' from the response with the '200' status
    • Potentially breaking GET /invites/{code} removed the optional property '/oneOf[#/components/schemas/GuildInviteResponse]/liveliness' from the response with the '200' status
  3. 1 breaking change
    • Breaking GET /guilds/{guild_id}/members added the pattern '^(0|[1-9][0-9]*)$' to the 'query' request parameter 'after'
  4. 30 breaking changes
    • Breaking POST /channels/{channel_id}/messages the '/allOf[#/components/schemas/MessageCreateRequest]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: multipart/form-data)
    • Breaking POST /channels/{channel_id}/messages the 'attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/json)
    • Breaking POST /channels/{channel_id}/messages the 'attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/x-www-form-urlencoded)
    • Breaking PATCH /channels/{channel_id}/messages/{message_id} the '/allOf[#/components/schemas/MessageEditRequestPartial]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: multipart/form-data)
    • Breaking PATCH /channels/{channel_id}/messages/{message_id} the 'attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/json)
    • Breaking PATCH /channels/{channel_id}/messages/{message_id} the 'attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/x-www-form-urlencoded)
    • Breaking POST /channels/{channel_id}/threads the '/anyOf[#/components/schemas/CreateForumThreadRequest]/message/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/json)
    • Breaking POST /channels/{channel_id}/threads the '/anyOf[#/components/schemas/CreateForumThreadRequest]/message/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: multipart/form-data)
    • Breaking POST /channels/{channel_id}/threads the '/anyOf[#/components/schemas/CreateForumThreadRequest]/message/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/x-www-form-urlencoded)
    • Breaking POST /interactions/{interaction_id}/{interaction_token}/callback the '/anyOf[#/components/schemas/CreateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookInteractionRequest]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/json)
    • Breaking POST /interactions/{interaction_id}/{interaction_token}/callback the '/anyOf[#/components/schemas/CreateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookInteractionRequest]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: multipart/form-data)
    • Breaking POST /interactions/{interaction_id}/{interaction_token}/callback the '/anyOf[#/components/schemas/CreateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookInteractionRequest]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/x-www-form-urlencoded)
    • Breaking POST /interactions/{interaction_id}/{interaction_token}/callback the '/anyOf[#/components/schemas/UpdateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookUpdateForInteractionCallbackRequestPartial]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: multipart/form-data)
    • Breaking POST /interactions/{interaction_id}/{interaction_token}/callback the '/anyOf[#/components/schemas/UpdateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookUpdateForInteractionCallbackRequestPartial]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/x-www-form-urlencoded)
    • Breaking POST /interactions/{interaction_id}/{interaction_token}/callback the '/anyOf[#/components/schemas/UpdateMessageInteractionCallbackRequest]/data/oneOf[#/components/schemas/IncomingWebhookUpdateForInteractionCallbackRequestPartial]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/json)
    • Breaking POST /lobbies/{lobby_id}/messages the 'attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/x-www-form-urlencoded)
    • Breaking POST /lobbies/{lobby_id}/messages the 'attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: multipart/form-data)
    • Breaking POST /lobbies/{lobby_id}/messages the 'attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/json)
    • Breaking POST /webhooks/{webhook_id}/{webhook_token} the '/anyOf[#/components/schemas/IncomingWebhookRequestPartial]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: multipart/form-data)
    • Breaking POST /webhooks/{webhook_id}/{webhook_token} the '/anyOf[#/components/schemas/IncomingWebhookRequestPartial]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/x-www-form-urlencoded)
    • Breaking POST /webhooks/{webhook_id}/{webhook_token} the '/anyOf[#/components/schemas/IncomingWebhookRequestPartial]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/json)
    • Breaking POST /webhooks/{webhook_id}/{webhook_token} the '/anyOf[#/components/schemas/IncomingWebhookUpdateRequestPartial]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/json)
    • Breaking POST /webhooks/{webhook_id}/{webhook_token} the '/anyOf[#/components/schemas/IncomingWebhookUpdateRequestPartial]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: application/x-www-form-urlencoded)
    • Breaking POST /webhooks/{webhook_id}/{webhook_token} the '/anyOf[#/components/schemas/IncomingWebhookUpdateRequestPartial]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: multipart/form-data)
    • Breaking PATCH /webhooks/{webhook_id}/{webhook_token}/messages/@original the '/allOf[#/components/schemas/IncomingWebhookUpdateRequestPartial]/attachments/items/filename' request property's minLength was increased from '0' to '1' (media type: multipart/form-data)
    • and 5 more
  5. 3 breaking changes
    • Breaking POST /partner-sdk/provisional-accounts/unmerge the 'external_auth_token' request property's minLength was increased from '0' to '1'
    • Breaking POST /partner-sdk/provisional-accounts/unmerge/bot the 'external_user_id' request property's minLength was increased from '0' to '1'
    • Breaking POST /partner-sdk/token the 'external_auth_token' request property's minLength was increased from '0' to '1'
  6. 1 breaking change
    • Breaking POST /guilds/{guild_id}/bulk-ban removed the success response with the status '204'
  7. 8 breaking changes
    • Breaking PATCH /channels/{channel_id} the '/anyOf[#/components/schemas/UpdateThreadRequestPartial]/rate_limit_per_user' request property type/format changed from 'integer, null'/'' to 'integer, null'/'int32'
    • Breaking POST /channels/{channel_id}/messages/{message_id}/threads the 'rate_limit_per_user' request property type/format changed from 'integer, null'/'' to 'integer, null'/'int32'
    • Breaking POST /channels/{channel_id}/threads the '/anyOf[#/components/schemas/CreateForumThreadRequest]/rate_limit_per_user' request property type/format changed from 'integer, null'/'' to 'integer, null'/'int32' (media type: application/json)
    • Breaking POST /channels/{channel_id}/threads the '/anyOf[#/components/schemas/CreateForumThreadRequest]/rate_limit_per_user' request property type/format changed from 'integer, null'/'' to 'integer, null'/'int32' (media type: application/x-www-form-urlencoded)
    • Breaking POST /channels/{channel_id}/threads the '/anyOf[#/components/schemas/CreateForumThreadRequest]/rate_limit_per_user' request property type/format changed from 'integer, null'/'' to 'integer, null'/'int32' (media type: multipart/form-data)
    • Breaking POST /channels/{channel_id}/threads the '/anyOf[#/components/schemas/CreateTextThreadWithoutMessageRequest]/rate_limit_per_user' request property type/format changed from 'integer, null'/'' to 'integer, null'/'int32' (media type: application/json)
    • Breaking POST /channels/{channel_id}/threads the '/anyOf[#/components/schemas/CreateTextThreadWithoutMessageRequest]/rate_limit_per_user' request property type/format changed from 'integer, null'/'' to 'integer, null'/'int32' (media type: application/x-www-form-urlencoded)
    • Breaking POST /channels/{channel_id}/threads the '/anyOf[#/components/schemas/CreateTextThreadWithoutMessageRequest]/rate_limit_per_user' request property type/format changed from 'integer, null'/'' to 'integer, null'/'int32' (media type: multipart/form-data)
  8. 9 breaking changes
    • Breaking GET /channels/{channel_id}/invites added 'subschema #20: PRUNE_REQUIRES_ADMIN' to the '/items/oneOf[#/components/schemas/GuildInviteResponse]/guild/features/items/' response property 'oneOf' list for the response status '200'
    • Breaking POST /channels/{channel_id}/invites added 'subschema #20: PRUNE_REQUIRES_ADMIN' to the '/oneOf[#/components/schemas/GuildInviteResponse]/guild/features/items/' response property 'oneOf' list for the response status '200'
    • Breaking GET /guilds/{guild_id} added 'subschema #20: PRUNE_REQUIRES_ADMIN' to the 'features/items/' response property 'oneOf' list for the response status '200'
    • Breaking PATCH /guilds/{guild_id} added 'subschema #20: PRUNE_REQUIRES_ADMIN' to the 'features/items/' response property 'oneOf' list for the response status '200'
    • Breaking GET /guilds/{guild_id}/invites added 'subschema #20: PRUNE_REQUIRES_ADMIN' to the '/items/oneOf[#/components/schemas/GuildInviteResponse]/guild/features/items/' response property 'oneOf' list for the response status '200'
    • Breaking GET /guilds/{guild_id}/preview added 'subschema #20: PRUNE_REQUIRES_ADMIN' to the 'features/items/' response property 'oneOf' list for the response status '200'
    • Breaking DELETE /invites/{code} added 'subschema #20: PRUNE_REQUIRES_ADMIN' to the '/oneOf[#/components/schemas/GuildInviteResponse]/guild/features/items/' response property 'oneOf' list for the response status '200'
    • Breaking GET /invites/{code} added 'subschema #20: PRUNE_REQUIRES_ADMIN' to the '/oneOf[#/components/schemas/GuildInviteResponse]/guild/features/items/' response property 'oneOf' list for the response status '200'
    • Breaking GET /users/@me/guilds added 'subschema #20: PRUNE_REQUIRES_ADMIN' to the '/items/features/items/' response property 'oneOf' list for the response status '200'
  9. 7 breaking changes, 60 potentially breaking
    • Breaking GET /applications/@me added 'subschema #40: ENTITLEMENT_CREATE, subschema #41: ENTITLEMENT_UPDATE, subschema #42: ENTITLEMENT_DELETE, subschema #48: LOBBY_MESSAGE_CREATE, subschema #49: LOBBY_MESSAGE_UPDATE, subschema #50: LOBBY_MESSAGE_DELETE, subschema #51: GAME_DIRECT_MESSAGE_CREATE, subschema #52: GAME_DIRECT_MESSAGE_DELETE, subschema #53: GAME_DIRECT_MESSAGE_UPDATE, subschema #59: APPLICATION_AUTHORIZED, subschema #60: APPLICATION_DEAUTHORIZED, subschema #78: QUEST_USER_ENROLLMENT' to the 'event_webhooks_types/items/allOf[#/components/schemas/ActionTypes]/' response property 'oneOf' list for the response status '200'
    • Breaking PATCH /applications/@me added 'subschema #40: ENTITLEMENT_CREATE, subschema #41: ENTITLEMENT_UPDATE, subschema #42: ENTITLEMENT_DELETE, subschema #48: LOBBY_MESSAGE_CREATE, subschema #49: LOBBY_MESSAGE_UPDATE, subschema #50: LOBBY_MESSAGE_DELETE, subschema #51: GAME_DIRECT_MESSAGE_CREATE, subschema #52: GAME_DIRECT_MESSAGE_DELETE, subschema #53: GAME_DIRECT_MESSAGE_UPDATE, subschema #59: APPLICATION_AUTHORIZED, subschema #60: APPLICATION_DEAUTHORIZED, subschema #78: QUEST_USER_ENROLLMENT' to the 'event_webhooks_types/items/allOf[#/components/schemas/ActionTypes]/' response property 'oneOf' list for the response status '200'
    • Breaking GET /applications/{application_id} added 'subschema #40: ENTITLEMENT_CREATE, subschema #41: ENTITLEMENT_UPDATE, subschema #42: ENTITLEMENT_DELETE, subschema #48: LOBBY_MESSAGE_CREATE, subschema #49: LOBBY_MESSAGE_UPDATE, subschema #50: LOBBY_MESSAGE_DELETE, subschema #51: GAME_DIRECT_MESSAGE_CREATE, subschema #52: GAME_DIRECT_MESSAGE_DELETE, subschema #53: GAME_DIRECT_MESSAGE_UPDATE, subschema #59: APPLICATION_AUTHORIZED, subschema #60: APPLICATION_DEAUTHORIZED, subschema #78: QUEST_USER_ENROLLMENT' to the 'event_webhooks_types/items/allOf[#/components/schemas/ActionTypes]/' response property 'oneOf' list for the response status '200'
    • Breaking PATCH /applications/{application_id} added 'subschema #40: ENTITLEMENT_CREATE, subschema #41: ENTITLEMENT_UPDATE, subschema #42: ENTITLEMENT_DELETE, subschema #48: LOBBY_MESSAGE_CREATE, subschema #49: LOBBY_MESSAGE_UPDATE, subschema #50: LOBBY_MESSAGE_DELETE, subschema #51: GAME_DIRECT_MESSAGE_CREATE, subschema #52: GAME_DIRECT_MESSAGE_DELETE, subschema #53: GAME_DIRECT_MESSAGE_UPDATE, subschema #59: APPLICATION_AUTHORIZED, subschema #60: APPLICATION_DEAUTHORIZED, subschema #78: QUEST_USER_ENROLLMENT' to the 'event_webhooks_types/items/allOf[#/components/schemas/ActionTypes]/' response property 'oneOf' list for the response status '200'
    • Breaking POST /guilds/{guild_id}/roles the 'name' request property's minLength was increased from '0' to '1'
    • Breaking PATCH /guilds/{guild_id}/roles/{role_id} the 'name' request property's minLength was increased from '0' to '1'
    • Breaking GET /oauth2/applications/@me added 'subschema #40: ENTITLEMENT_CREATE, subschema #41: ENTITLEMENT_UPDATE, subschema #42: ENTITLEMENT_DELETE, subschema #48: LOBBY_MESSAGE_CREATE, subschema #49: LOBBY_MESSAGE_UPDATE, subschema #50: LOBBY_MESSAGE_DELETE, subschema #51: GAME_DIRECT_MESSAGE_CREATE, subschema #52: GAME_DIRECT_MESSAGE_DELETE, subschema #53: GAME_DIRECT_MESSAGE_UPDATE, subschema #59: APPLICATION_AUTHORIZED, subschema #60: APPLICATION_DEAUTHORIZED, subschema #78: QUEST_USER_ENROLLMENT' to the 'event_webhooks_types/items/allOf[#/components/schemas/ActionTypes]/' response property 'oneOf' list for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'APPLICATION_AUTHORIZED' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'APPLICATION_DEAUTHORIZED' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'ENTITLEMENT_CREATE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'ENTITLEMENT_DELETE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'ENTITLEMENT_UPDATE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'GAME_DIRECT_MESSAGE_CREATE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'GAME_DIRECT_MESSAGE_DELETE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'GAME_DIRECT_MESSAGE_UPDATE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'LOBBY_MESSAGE_CREATE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'LOBBY_MESSAGE_DELETE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'LOBBY_MESSAGE_UPDATE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking GET /applications/@me added the new 'QUEST_USER_ENROLLMENT' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking PATCH /applications/@me added the new 'APPLICATION_AUTHORIZED' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking PATCH /applications/@me added the new 'APPLICATION_DEAUTHORIZED' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking PATCH /applications/@me added the new 'ENTITLEMENT_CREATE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking PATCH /applications/@me added the new 'ENTITLEMENT_DELETE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking PATCH /applications/@me added the new 'ENTITLEMENT_UPDATE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • Potentially breaking PATCH /applications/@me added the new 'GAME_DIRECT_MESSAGE_CREATE' enum value to the 'event_webhooks_types/items/' response property for the response status '200'
    • and 42 more
  10. 85 potentially breaking
    • Potentially breaking POST /applications/{application_id}/attachment removed the optional property 'attachment/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages removed the optional property '/items/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages removed the optional property '/items/message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages removed the optional property '/items/referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages removed the optional property '/items/referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking POST /channels/{channel_id}/messages removed the optional property 'attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking POST /channels/{channel_id}/messages removed the optional property 'message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking POST /channels/{channel_id}/messages removed the optional property 'referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking POST /channels/{channel_id}/messages removed the optional property 'referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages/pins removed the optional property 'items/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages/pins removed the optional property 'items/items/message/message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages/pins removed the optional property 'items/items/message/referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages/pins removed the optional property 'items/items/message/referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages/{message_id} removed the optional property 'attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages/{message_id} removed the optional property 'message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages/{message_id} removed the optional property 'referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking GET /channels/{channel_id}/messages/{message_id} removed the optional property 'referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking PATCH /channels/{channel_id}/messages/{message_id} removed the optional property 'attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking PATCH /channels/{channel_id}/messages/{message_id} removed the optional property 'message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking PATCH /channels/{channel_id}/messages/{message_id} removed the optional property 'referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking PATCH /channels/{channel_id}/messages/{message_id} removed the optional property 'referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking POST /channels/{channel_id}/messages/{message_id}/crosspost removed the optional property 'attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking POST /channels/{channel_id}/messages/{message_id}/crosspost removed the optional property 'message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking POST /channels/{channel_id}/messages/{message_id}/crosspost removed the optional property 'referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/attachments/items/clip_events_timeline' from the response with the '200' status
    • Potentially breaking POST /channels/{channel_id}/messages/{message_id}/crosspost removed the optional property 'referenced_message/oneOf[#/components/schemas/BasicMessageResponse]/message_snapshots/items/message/attachments/items/clip_events_timeline' from the response with the '200' status
    • and 60 more
  11. 1 breaking change
    • Breaking POST /partner-sdk/token/bot the 'external_user_id' request property's minLength was increased from '0' to '1'

Frequently asked questions

Has the Discord API had breaking changes recently?
Yes: 6 breaking changes and 1 deprecation in the last 90 days. The most recent is “Custom Status Hidden by Profile Privacy Settings” from 17 September 2026.
How often does the Discord API change?
Over the period on record, Discord published about 3 changelog entries a month. Most are additions; the breaking changes and deprecations are the ones to plan for.
Where is the official Discord API changelog?
Discord publishes it at https://discord.com/developers/docs/change-log. This page follows it daily and dates each entry.
How do I get notified about Discord API changes?
Subscribe to this page's RSS feed (https://seamless.engineering/api-changelog/discord/rss.xml). If you would rather have someone act on them, we operate Discord integrations and handle changes like these before they reach production.

Other APIs we monitor

// scoping request

We watch Discord because we run integrations on it. If one of yours depends on Discord, we can take it over: build it properly, operate it, and fix it when Discord changes, before your data is affected. Fixed-price scoping quote within 48 hours.

We reply within one working day. No newsletter, no sales sequence.