Get User By User group
The Get User By User group will filter and search User options based on provided search values.
Resource Informations
Name | Value |
---|---|
Requires authentication? | Yes |
Rate limited? | No |
Request
Request headers
Key | Value |
---|---|
Authorization | Bearer token |
Content-Type | application/json |
HTTP request URL for SSMS
GET https://{hostname}/auth/realms/{tenantId}/v3_client/groups/{groupId}/users?
limit=1&offset=1&isUserEnabled=boolean&orderBy=desc&orderByKey=lastname&genericSearchVal={string}&fromDate={timestampinmillisecond}&toDate={timestampinmillisecond}
HTTP request URL for SHIFT
GET https://{hostname}/auth/realms/{tenantId}/v3_client/groups/{groupId}/users?
limit=1&offset=1&isUserEnabled=boolean&orderBy=desc&orderByKey=lastname&genericSearchVal={string}&fromDate={timestampinmillisecond}&toDate={timestampinmillisecond}
note
API requests must be made over https. Calls made over plain http will fail.
Parameters
Parameter Name | Type | Description |
---|---|---|
limit | Integer | provide limit |
offset | Integer | provide offset |
isUserEnabled | Boolean | Enable user. Per Default false |
genericSearchVal | String | It is a customized search for first name, last name, email, or username, and if the search is empty, we will consider the firstname, lastname, email, and username parameters, else these four parameters will be ignored. |
orderBy | String | Provide "asc or desc" to order it. |
orderByKey | String | firstName or lastName or email or username or createdTimestamp (to provide each user's creation time) |
fromDate | long | To fetch the user data based on the date of createdTimestamp in milliseconds. |
toDate | long | To fetch the user data based on the date until which users have been createdTimestamp in milliseconds. |
Request body
No request body fields are required.
Response
Field Name | Type | Description |
---|---|---|
message | String | Message explains result of the API call. Refer Response status Information for details. |
status | String | The status of the API call. Refer Response status Information for details. |
subSystem | Integer | subSystem categorizes the type of API that has been called. Refer Subsystem details for details. |
data | Object | User Profile Information |
Sample Response
{
"message": "Users fetched successfully",
"status": "Success",
"subSystem": 5,
"data": {
"userList": [
{
"username": "akash@gmail.com",
"id": "fee8916c-b4e4-407a-b00d-840b67090189",
"email": "akash@gmail.com",
"firstName": "Akash",
"lastName": "M",
"createdTimestamp": 1684214923416,
"enabled": true,
"emailVerified": false,
"attributes": {
"firstName": [
"Akash"
],
"lastName": [
"M"
],
"email": [
"akash@gmail.com"
],
"status": [
"REGISTRATION_INCOMPLETE"
],
"linkedAstClientIds": [
"[\"01G2MBNMBEE94EYSD200KE9JAX\"]"
],
"username": [
"akash@gmail.com"
]
},
"requiredActions": [
"kobil-reg-status-required-action"
],
"admin": false
}
],
"page": {
"pageSize": 100,
"totalRecords": 53,
"totalPages": 1,
"currentPage": 1
}
}
}
Response Status Information
Status Code | Status | Message |
---|---|---|
200 | Success | Users fetched successfully |
400 | BAD_REQUEST | USER_NOT_FOUND |
401 | Unauthorized | HTTP 401 Unauthorized |
404 | Not Found | Not Found |