[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-discord-api-changelog-2026-07-17-applicationresponse-adds-required-field-eligible-oauth2":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"discord-api-changelog","Discord API","discord","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fdiscord\u002Fdiscord-api-spec\u002Fmain\u002Fspecs\u002Fopenapi.json",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KXRY2RGFKVPERKRAQ3P27WT9","2026-07-17-applicationresponse-adds-required-field-eligible-oauth2","Breaking","ApplicationResponse adds required field eligible_oauth2_scopes","A new field **`eligible_oauth2_scopes`** (array of `OAuth2Scopes`) has been added to the `ApplicationResponse` schema and placed in the `required` array. Because it is marked required, clients that validate response payloads against this schema (e.g. strict deserializers or generated SDK models) may break if they receive older responses lacking this field, or if server responses that now include it are not handled. Clients writing back this schema shape also need to be aware of the new required field.","2026-07-17T21:00:23.951Z"]