Description
Activate an inactive user group. Activation is a dedicated action rather than a field, so the active state cannot be changed through PUT | Update user group or PATCH | Partially update user group.
An update sent to an inactive group is refused with 409 api.resource.inactive, so activate the group first when you need to edit it.
Prerequisites
- An application with the Users authorization granted by the administrator in A2A. For more information, access How to manage authorizations in A2A.
- A valid OAuth 2.0 access token. For more information, access How to authenticate an application in A2A.
Request
POST /api/v2/iam/user-groups/{id}/activate
This action takes no request body.
Path parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
id |
integer | Yes | Unique identification code of the user group. |
Example request
POST {{url}}/api/v2/iam/user-groups/7/activate
Response
HTTP/1.1 204 No Content
X-Request-Id: 7f3c1a90-2c4e-4b1a-9f5e-0a2b7c9d1e34
A successful activation returns no body. To confirm the new state, access GET | List a user group.
Activation does not restore memberships. Deactivating or deleting a group removes all of its members, so add them again after activation. For more information, access POST | Add members to a user group.
Errors
| HTTP code | Message | Possible cause | Solution |
|---|---|---|---|
401 |
api.auth.unauthorized |
The access token is missing, invalid, or has expired. | Request a new access token. |
404 |
api.resource.not_found |
The user group does not exist, or it is outside the scope of the authorization. | Check the identification code and the authorization scope. |
409 |
api.resource.conflict.already_active |
The user group is already active. | No action is required. |
429 |
api.rate_limit_exceeded |
The request rate limit was exceeded. | Wait the number of seconds returned in the Retry-After header and try again. |
For authentication error messages and the 403 versus 404 policy, access API v2 - Conventions and shared behaviors.