GET /user-management-v2/users/{userId}/roles/{roleId}/
FROM API REVISION 6.0
This resource returns the role details.
Used when you are operating a browser without access to the header parameter. This allows you to choose which encoding you want to use for the response:
All these resources can be used according what the resource allows.
To address the raw value of a primitive property, clients append a path segment containing the string $value to the property URL.
To use this query option you need to use the classic resource and add the element name you want to print followed by the query string name.
<span class="warning"><span class="glyphicon glyphicon-warning-sign" aria-hidden="true"> Be careful, the parameter query string is used in the URL and is not like other parameters.
The $select system query option allows clients to request a limited set of properties for each entity.
The value pass in the parameter can be:
*
"(star): This will show all child elements.,
" (comma).If there is no value after the select query option, the parameter will be ignored. All the values that are not specified will not be printed in the response.
If this parameter is not in the request, the Application/Json will be chosen by default.
There are multiple possible values (according the resource):
The first two are the most often used.
Object Name: Role
Property Name | Type | Description | Method |
---|---|---|---|
Id | Integer | This is the role's ID. | GET |
Name | String | This is the role's name. It can be :
|
GET POST |
URL Example: https://0.0.0.0/api/rest/v1/user-management-v2/users/1/roles/1
{
"id": 1,
"name": "Admin"
}
URL Example: https://0.0.0.0/api/rest/v1/user-management-v2/users/1/roles/1
<?xml version="1.0" encoding="utf-8"?>
<Role>
<Id>1</Id>
<Name>Admin</Name>
</Role>