List group members
GET/groups/:groupName/members
Returns the users in a group.
Everyone listed here holds every permission set assigned to the group;
GET /groups/{groupName}/assignments is what that amounts to.
There is no pagination, and there is a ceiling. At most 500 members
come back, and a larger group is truncated silently: no flag, no total,
nothing in the body to distinguish a group of exactly 500 from a group of
5000. Treat a count of 500 as "at least 500".
Members are returned in Prism's own four-field summary form, the same
shape GET /users lists, not the directory's user representation. To
see everything one of them can reach, including access that does not come
from this group, call GET /users/{username}/effective-assignments.
Request
Responses
- 200
- 401
- 403
- 404
- 500
The group's members. A group that exists but is empty is a 200 with
an empty members array.
Authentication failed: the X-API-Token header was missing, malformed,
expired or not recognised.
This response is text/plain, not JSON. It is written by
http.Error in the authentication middleware, which runs before any
handler and therefore before anything that would build a JSON envelope.
A client that unconditionally JSON-parses response bodies will fail on
this one, so check the status code first.
The token is valid, but it is not allowed to act on this tenant.
An API token is minted inside one tenant and stays bound to it for life.
Sending it to a path whose tenant segment names a different tenant is
refused here, in middleware, before the operation runs, so this says
nothing about the resource you asked for, only about which tenant the
path named. Check the tenant server variable against the console the
token was created in.
No group in your tenant has this name. Note that the two mutating operations on this same path report an unknown group as a 500 instead.
The members could not be read from the directory.