[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fCbkW4RdHf1epvpYD88cAaGqf672L_fSZ1LJERMVzJU4":3,"$fIibzf03KxXEp0gniAJmoWSmD3WYlbPlpXFG8EcRtQSs":21},{"status":4,"source":5,"previous":12,"current":16,"newerSnapshotId":20,"olderSnapshotId":13},"has-previous",{"id":6,"displayName":7,"vendor":8,"kind":9,"apiType":10,"url":11},"discord-api-changelog","Discord API","discord","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fdiscord\u002Fdiscord-api-spec\u002Fmain\u002Fspecs\u002Fopenapi.json",{"id":13,"contentHash":14,"fetchedAt":15},"01KX267P27NVRT441VFXHJ9E6R","8057fc7ac2194d5f6a599e7facc716a06c8fdd5e07be885a84e5340a6b7277c7","2026-07-09T01:00:21.354Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KX4N68NBZ1Q4V3CMWJ5VJXHM","44b84f6e3d3bf1d15654dcaf1a514edce5b5f0bb32cd3ce6e57bd62dbb8ada83","2026-07-10T00:00:12.454Z",null,{"alerts":22},[23,30,37,44,51,58,65,72,79,87,94],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":18,"detectedAt":28,"slug":29},"01KX4N6HPC5P7B73DXAN7ABXF1","Informational","Remove 204 response spec from bulk_ban_users_from_guild","The `204` response definition (with rate-limit headers) was removed from the `POST \u002Fguilds\u002F{guild_id}\u002Fbulk-ban` (`bulk_ban_users_from_guild`) operation in the OpenAPI spec. This is a spec-only correction — the actual API likely never returns a bare `204` for this endpoint (it returns `200` with body data), so removing the erroneous response definition brings the spec closer to reality without changing real API behaviour.","2026-07-10T00:00:22.220Z","2026-07-10-remove-204-response-spec-from-bulk-ban-users-from-guild",{"id":31,"severity":32,"title":33,"summary":34,"contentHash":14,"detectedAt":35,"slug":36},"01KX267T5N47DHJHG367VE4SPB","Additive","Add optional liveliness field to invite object","The invite object schema now includes an optional `liveliness` field that returns a new `GuildLivelinessResponse` object containing guild message activity data. This is a purely additive change that does not affect existing integrations.","2026-07-09T01:00:26.165Z","2026-07-09-add-optional-liveliness-field-to-invite-object",{"id":38,"severity":25,"title":39,"summary":40,"contentHash":41,"detectedAt":42,"slug":43},"01KWBN85BY3Y88CA31Y4XJ49JG","Add int32 format annotation to integer fields","Added `\"format\": \"int32\"` annotation to four integer fields with `maximum: 21600` constraint across the Discord API specification. This is a documentation enhancement that clarifies the type representation in the OpenAPI schema without changing runtime behavior or field semantics.","cf73eb3de3a0b352c1ed3b59b12172152d70f83ec16b844e7836ce2a9d4acc28","2026-06-30T07:00:14.334Z","2026-06-30-add-int32-format-annotation-to-integer-fields",{"id":45,"severity":32,"title":46,"summary":47,"contentHash":48,"detectedAt":49,"slug":50},"01KW0TG2E25YBAAVW6NRYBJKJ9","Add target_channel_id and target_message_id to invite API","Added two new optional query parameters (`target_channel_id` and `target_message_id`) to invite-related endpoints, and corresponding response fields to the invite schema. These are purely additive fields that do not affect existing integrations.","c683b9551d6f259def363ab60b9432d47f2350465b32f54ceec129c63e4002c7","2026-06-26T02:00:17.602Z","2026-06-26-add-target-channel-id-and-target-message-id-to-invite-api",{"id":52,"severity":32,"title":53,"summary":54,"contentHash":55,"detectedAt":56,"slug":57},"01KVTXNH2QCB3NPN7CEKWQEJXW","Add optional is_spoiler field to audit log entries","A new optional `is_spoiler` field (boolean or null) has been added to the audit log entry schema. This is a backwards-compatible addition that allows clients to optionally read spoiler information from audit log changes.","d275bd0b41d9c5cfe41c26935ab7f0a39e040d466531844b2d5d8777409b243d","2026-06-23T19:00:15.575Z","2026-06-23-add-optional-is-spoiler-field-to-audit-log-entries",{"id":59,"severity":32,"title":60,"summary":61,"contentHash":62,"detectedAt":63,"slug":64},"01KVSA5JNZ6ME1RMT84WH9BJHP","Add PRUNE_REQUIRES_ADMIN guild feature","A new guild feature flag `PRUNE_REQUIRES_ADMIN` has been added to indicate when a guild has restricted member prune operations to administrators and the guild owner. This is an additive change that introduces a new enum constant without affecting existing functionality.","9d9835a65e9c04d4e4ad62e73445f12deafcd54694b80c42427c16b5bdff7e57","2026-06-23T04:00:15.551Z","2026-06-23-add-prune-requires-admin-guild-feature",{"id":66,"severity":32,"title":67,"summary":68,"contentHash":69,"detectedAt":70,"slug":71},"01KV6VN35JE6QM9KP4YDJYSZFR","Add role_ids field to message interaction callback","A new optional `role_ids` field has been added to the CreateMessageInteractionCallbackRequest schema. It accepts a string, array of Snowflake IDs (up to 250 unique items), or null. This allows filtering message visibility by roles in interaction responses.","186f6a6ce33bd8b9dc63728845ee9378a0572423388bcad30abd8163538a9f07","2026-06-16T00:00:15.538Z","2026-06-16-add-role-ids-field-to-message-interaction-callback",{"id":73,"severity":25,"title":74,"summary":75,"contentHash":76,"detectedAt":77,"slug":78},"01KTZBAN8M0H2WXSJVT41J1X8P","Rename BasicApplicationResponse to BasicApplicationResponseWithBot","The schema `BasicApplicationResponse` has been renamed to `BasicApplicationResponseWithBot` throughout the OpenAPI spec. This is a documentation\u002Fnaming change that clarifies the schema's purpose and is reflected in the message response schemas that reference it, but does not alter the actual API behaviour or response structure for clients.","703bb740cb521aa3ef92fef52b19a280145d15543c5a84682ee3b03f688e375d","2026-06-13T02:00:15.380Z","2026-06-13-rename-basicapplicationresponse-to",{"id":80,"severity":81,"title":82,"summary":83,"contentHash":84,"detectedAt":85,"slug":86},"01KTYXKCZAFA4FZ746HBHDHS26","Breaking","InviteChannelRecipientResponse now requires id and avatar fields","The `InviteChannelRecipientResponse` schema adds two new **required** fields: `id` (SnowflakeType) and `avatar` (nullable string). While these are new response fields (additive in terms of data), marking them as `required` means any client-side schema validation or strict deserialization that previously only expected `username` will now fail if it enforces the required list — and any mock\u002Fstub implementations that don't return these fields will be considered non-compliant. Existing clients that simply read the response are unaffected, but strict validators will break.","6a451326e6e0fcfa1a45d1af8f7e9b12b198717ad93d90b16619f83cd017a9c3","2026-06-12T22:00:21.738Z","2026-06-12-invitechannelrecipientresponse-now-requires-id-and-avatar",{"id":88,"severity":32,"title":89,"summary":90,"contentHash":91,"detectedAt":92,"slug":93},"01KTD3P1JKEDZPDAJBJBBBN9ZP","Add scheduled event recurrence and exceptions support","The Discord API adds support for recurring guild scheduled events with new `recurrence_rule` fields, exception handling endpoints, and a new `\u002Fguilds\u002F{guild_id}\u002Fincident-actions` endpoint. New schema types `UserProfileRuleResponse`, `UserProfileUpsertRequest`, `UserProfileUpsertRequestPartial`, `GuildIncidentActionsRequest`, `GuildIncidentsDataResponse`, `GuildScheduledEventExceptionCreateRequest`, `RecurrenceRule`, and `RecurrenceRuleResponse` are introduced. All existing endpoints and fields remain functional—this release is purely additive.","693bf1f99bba28f0ab8e763c437aa7e50a9b7c3997d32ec06986f59fdccf4e50","2026-06-06T00:00:20.051Z","2026-06-06-add-scheduled-event-recurrence-and-exceptions-support",{"id":95,"severity":32,"title":96,"summary":97,"contentHash":98,"detectedAt":99,"slug":100},"01KS9CDDYJGFZESG31YFGS0RKA","Add optional provisional_user_id field to API response","A new optional response field `provisional_user_id` (nullable or Snowflake ID) has been added to an API response object. This is additive and will not break existing clients that do not depend on this field.","b5b13e5b3535174594330f88ac5f560863e53c4dbc72b13b87c84f097fc78a1e","2026-05-23T03:00:15.442Z","2026-05-23-add-optional-provisional-user-id-field-to-api-response"]