[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-discord-api-changelog-2026-06-12-invitechannelrecipientresponse-now-requires-id-and-avatar":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},"01KTYXKCZAFA4FZ746HBHDHS26","2026-06-12-invitechannelrecipientresponse-now-requires-id-and-avatar","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.","2026-06-12T22:00:21.738Z"]