GET /api/0/projects/.../users/ response schema expanded with required fields
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
The GET /api/0/projects/{organization_id_or_slug}/{project_id_or_slug}/users/ 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/email may need to handle the new shape, and tooling that validated the old minimal schema will now see unexpected required fields.