POST
/v1/mgmt/group/members

Authorization

Descope Project ID and Management Key
AuthorizationBearer <token>

Project ID:Management Key as bearer token.

In: header

Request Body

application/json

tenantId?string
groupId?string
ssoId?string

Optional: return the group only if it came from this SSO configuration (ssoId). Use the reserved id "default_ssoid" for the tenant's default SSO configuration.

Load all members of a specific External group, using a valid management key.

This API endpoint allows administrators to load all members of a specific external group that is associated to a tenant. The response contains an array of group objects including the group id, display name, and an array of associated members.

Next Steps

Administrators can review this information and make changes within their IdP or if necessary, Create a SCIM Group, Update an Existing SCIM Group (adding new members), or Delete an Existing SCIM Group

See also

  • See SSO Configuration for further details on managing SSO Configurations on a tenant.
curl -X POST "https://api.descope.com/v1/mgmt/group/members" \  -H "Content-Type: application/json" \  -d '{}'
{  "groups": [    {      "id": "string",      "display": "string",      "members": [        {          "loginId": "string",          "userId": "string",          "display": "string"        }      ],      "source": "string",      "ssoId": "string"    }  ]}
export interface Response {groups?: Group[]}export interface Group {id?: stringdisplay?: stringmembers?: GroupMember[]source?: string/** * The SSO configuration (ssoId) the group came from: the SSO config bound to the SCIM token that *  created it, or the SSO config used at the JIT login that persisted it. Groups from the tenant's *  default SSO configuration (and groups created before origin stamping existed) report the *  reserved id "default_ssoid". */ssoId?: string}export interface GroupMember {loginId?: stringuserId?: stringdisplay?: string}
Was this helpful?