[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-sentry-openapi-2026-06-05-get-api-0-projects-users-response-schema-expanded-with":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"sentry-openapi","Sentry API","sentry","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fgetsentry\u002Fsentry-api-schema\u002Fmain\u002Fopenapi-derefed.json",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KTAHA3TSQZ3HX2GQD9VPE4D6","2026-06-05-get-api-0-projects-users-response-schema-expanded-with","Breaking","GET \u002Fapi\u002F0\u002Fprojects\u002F...\u002Fusers\u002F response schema expanded with required fields","The `GET \u002Fapi\u002F0\u002Fprojects\u002F{organization_id_or_slug}\u002F{project_id_or_slug}\u002Fusers\u002F` endpoint's response schema was replaced with a much richer object. The old schema only required `username` (nullable) and `email` (nullable); the new schema requires **8 additional non-nullable fields**: `avatarUrl`, `dateCreated`, `hash`, `id`, `identifier`, `ipAddress`, `name`, and `tagValue`. Additionally, the required OAuth scope changed from `project:read` alone to `project:admin`, `project:read`, or `project:write`, and the `cursor` parameter now has `minLength: 1`. Clients that previously received only `username`\u002F`email` may need to handle the new shape, and tooling that validated the old minimal schema will now see unexpected required fields.","2026-06-05T00:00:45.913Z"]