Get User Group

DEPRECATED: These APIs have been deprecated. Please use Get Users by Group API for fetching information for a single group.

GET /v2/usermanagement/{orgId}/user-groups/{groupId}

This API retrieves the details of a single user-group within a specified organization by searching for them using their groupId. Successful queries will return a 200 response whose body is a single JSON response representing the user-group information.

Throttle Limits: Maximum 5 requests per minute per a client. See Throttling Limits for full details.

Parameters

This table summarizes the parameters and how they are provided:

Name Type Required Description
orgId path true The unique identifier for an organization. This is a string of the form A495E53@AdobeOrg where the prefix before the @ is a hexadecimal number. You can find this value as part of the URL path for the organization in the Admin Console or in the adobe.io console for your User Management integration.
groupId path true The id of the user-group.
x-api-key header true The API key specified in the Adobe IO Console for the UMAPI integration used to authorize this session. See the Getting Started documentation for details. The header name is X-Api-Key and this parameter is its value.
Authorization header true The OAuth token generated by the authorization server from the JWT exchange which starts every UMAPI session. (This token usually begins with the letters ‘ey’.) The header name is Authorization, and this parameter, preceded by the word ‘Bearer’ and a space, is its value, as in Authorization: Bearer ey....
Content-type header false Used to specify the content type of the request data. Must be application/json
X-Request-Id header false An arbitrary string used to identify the corresponding response to a request. If a header with this name is provided in the request, the exact same header will be included in the response to that request.

Responses

Content-Type: application/json

200 OK

The response body contains the specified user-group in JSON format including the groupId, name and userCount. Please note that fields can be missing if there are no values, i.e. there are no users so userCount will not be returned. User-groups can have administrators who have the ability to manage the user membership of the user-group. In these scenarios, the details of the admin group and admin member count will be included in the response.

Example

{
  "groupId": 39127441,
  "name": "TestUsergroup",
  "type": "USER_GROUP",
  "adminGroupId": "42073423",
  "adminGroupName": "39127441USERGROUP_ADMIN_GROUP_NAME_SUFFIX",
  "userCount": 2,
  "adminCount": "1",
  "isReadOnly": false
}

Schema Properties

adminCount: string
The number of users with administrative privileges.

adminGroupId: string

adminGroupName: string

groupId: integer

name: string

type: string
The group type which will always be USER_GROUP.

userCount: integer
The number of users in the group.

isReadOnly: boolean Indicates if it is possible to directly add and remove users from the group. Groups shared from another organization will return true otherwise it will return false or not be present if not applicable. Further information is available at Share User Groups

Schema Model

{
    "adminCount": "string",
    "adminGroupId": "string",
    "adminGroupName": "string",
    "groupId": integer,
    "name": "string",
    "type": "string",
    "userCount": integer,
    "isReadOnly": boolean
  }

400 Bad Request

Some parameters of the request were not understood by the server or the Service Account Integration certificate has expired.

401 Unauthorized

Possible causes are:

  • Invalid or expired token.
  • Invalid Organization.
< HTTP/1.1 401 Unauthorized
< Content-Type: */*
< Date: Thu, 22 Jun 2017 09:47:04 GMT
< WWW-Authenticate: Bearer realm="JIL", error="invalid_token", error_description="The access token is invalid"
< X-Request-Id: user-assigned-request-id
< Content-Length: 0
< Connection: keep-alive

403 Forbidden

Possible causes are:

  • Missing API key.
  • The organization is currently migrating. Either from DMA or to One Console.
  • API key is not permitted access.
< HTTP/1.1 403 Forbidden
< Date: Thu, 22 Jun 2017 09:41:22 GMT
< X-Request-Id: user-assigned-request-id
< Content-Length: 0
< Connection: keep-alive

404 Not Found

The user-group was not found in the given organization.

< HTTP/1.1 404 Not Found
< Content-Type: application/json
< Date: Thu, 22 Jun 2017 09:39:06 GMT
< Vary: Accept-Encoding
< X-Request-Id: user-assigned-request-id
< Content-Length: 64
< Connection: keep-alive
<
{"errorMessage":"GROUP_NOT_FOUND","errorCode":"GROUP_NOT_FOUND"}

Example Requests

 curl -ivs -X GET \
   http://usermanagement.adobe.io/v2/usermanagement/28E1E2EB570F90057F000101@AdobeOrg/user-groups/39127441 \
   -H 'authorization: Bearer {ACCESS_TOKEN}' \
   -H 'content-type: application/json' \
   -H 'x-request-id: user-assigned-request-id' \

Throttling

To protect the availability of the Adobe back-end user identity systems, the User Management API imposes limits on client access to the data. Limits apply to the number of calls that an individual client can make within a time interval, and global limits apply to access by all clients within the time period. For this API the throttling limits are as follows:

  • Maximum calls per client: 5 requests per a minute
  • Maximum calls for the application: 50 requests per a minute

When the client or global access limit is reached, further calls fail with HTTP error status 429 Too Many Requests. The Retry-After header is included in the 429 response, and provides the minimum amount of time that the client should wait until retrying. See RFC 7231 for full information.

The User Management API recommends limiting your syncs to two hourly intervals and consider scheduling your sync for a time that works best for you, taking into account other timezones and clients. This will help to prevent how often your client is throttled.

The following sample shows a 429 response with the Retry-After header detailing the number of seconds to wait before retry:

========================= RESPONSE =========================
Status code: 429
-------------------------- header --------------------------
Content-Type: application/json
Date: Fri, 19 Jan 2018 10:31:43 GMT
Retry-After: 38
Server: APIP
X-Request-Id: iEUtsLiFgj3R4xsbirAyZlMyaxRTo8Xo
Content-Length: 54
Connection: keep-alive
--------------------------- body ---------------------------
{
  "error_code" : "429050",
  "message" : "Too many requests"
}
============================================================

Because of the global limits, and because the specific limits may change, you cannot simply limit the rate at which you make your own calls. You must handle rate-limit errors by retrying the failed calls. We recommend an exponential backoff retry technique for handling such errors.

Handling error responses

When you retry a failed request, the retry can also fail, and can fall back into the retry loop, adding to the system overload. The exponential backoff retry method increases the period between retries, so that the client makes fewer calls while the system is overloaded.

To implement an exponential backoff method, you increase the retry interval with each failed request. You should retry sending the request after a certain number of seconds, and increase that interval by a random amount with each attempt. For example, you can double the retry period each time, or escalate it by a power of 2, and then add a small random delay between failures.

A small random delay, known as “jitter,” prevents the “herd effect” that can occur if many clients attempt to reconnect to a recovering system at the same time. Without jitter, all of the retries could occur after 20 seconds, then 40 seconds, and so on. With the jitter, different retries occur at slightly different intervals. This allows the system to recover without further overloading it.

For an example of how to implement this error-handling method, see “Retrying Requests” in the User Management Walkthrough.