Get a team member
/v1/teams/{team}/members/{member} in the Team Members API.
curl https://api.example.test/v1/teams/$TEAM_ID/members/$USER_ID \ -H "Authorization: Bearer $TOKEN"One member, with their email, which this route always includes because it requires team-member:view by definition. 404 RESOURCE_NOT_FOUND if the user is not on the team or the team is not in the caller's visibility set.
role_idpoints at a role on the same team, ornullfor the owner pseudo-row;roleis that role's code,adminfor the owner.is_owneristrueonly for the team's creator, who is returned alongside the members but bypasses the membership table entirely.
Requires ability
The token must hold this ability, or the call is refused with 403.
Authorization
bearerToken A personal access token minted in the app under Account Settings, then API Tokens, sent as Authorization: Bearer zg_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team, and optionally to one project, at mint time.
In: header
Path Parameters
The team, resolved by the route binder.
uuidThe person's place on the team, resolved by the route binder.
Responses
200OKapplication/json
The membership.
401UnauthorizedAUTHENTICATION_REQUIREDapplication/json
The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (a zg_test_ token on production).
403ForbiddenTOKEN_MISSING_ABILITYapplication/json
The token is valid but does not carry the ability this endpoint requires; error.context.required_ability names the one to grant. An endpoint that also checks who registered a row answers FORBIDDEN with the same status, and says so in its own description.
404Not foundRESOURCE_NOT_FOUNDapplication/json
An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.
429Too many requestsRATE_LIMITEDapplication/json
The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.
How is this guide?
Last updated on