[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-discord-api-changelog-2026-07-16-minlength-1-added-to-a-string-field-max-1024-in-discord-api":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},"01KXP1CG9CXQWKPQ4XYMWS7AAV","2026-07-16-minlength-1-added-to-a-string-field-max-1024-in-discord-api","Breaking","minLength: 1 added to a string field (max 1024) in Discord API spec","A `\"minLength\": 1` constraint was added to a string field that previously had only a `maxLength` of 1024. This means empty strings (`\"\"`) are no longer valid for this field — clients sending empty strings will receive a validation error. The exact endpoint and field path are not shown in the diff context, but this is a tightening of an existing constraint.","2026-07-16T18:00:25.644Z"]