[Deprecated]: Get all users for a study
get
/ec-auth-svc/rest/v3.0/authstudies/{StudyID}/users
Deprecated: This version of the endpoint is deprecated. Use the v4 API at '/v4.0/authstudies/{StudyID}/users' instead. The v4 endpoint provides paginated, filterable user listings for a study, supports richer search, and returns the latest response structure with more complete user access details. Migrating to the new version ensures all output fields are compliant with the latest schema updates. Prior response structure is less detailed and may omit some child DTO fields.
Request
Path Parameters
-
StudyID(required): string
Study IDExample:
ABE31741A0E945F6B827048B279F2F19
Query Parameters
-
firstResult: integer(int32)
Offset from where the results should be retrievedExample:
3 -
isLiteAPI: boolean
Returns a lighter version of response consisting of user details.Default Value:
falseExample:false -
rowsToReturn: integer(int32)
Limit for the number of results to be returnedExample:
10 -
searchString: string
Given name or family name of the user to filter the results.Example:
Jon -
sortBy: array[string]
Sort byExample:
{ "value":[ "ADMIN", "DESIGNER" ] } -
viewMode: string
Mode of the study. Accepts active, test, or trainingAllowed Values:
[ "design", "test", "training", "active", "all" ]Example:design
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Success
Root Schema : DisplayStudyUserListDtoV2
Type:
objectTitle:
DisplayStudyUserListDtoV2Contains list of users information
Show Source
-
firstUserReturned: integer
(int32)
Index of the first user returned in this page.Example:
1 -
users: object
users
Version 2: Extends DisplayStudyUserDto to include user email and phone information.
-
usersFound: integer
(int32)
The total number of users found matching the query.Example:
2 -
usersReturned: integer
(int32)
How many users are present in this response.Example:
2
Nested Schema : users
Type:
objectVersion 2: Extends DisplayStudyUserDto to include user email and phone information.
Show Source
-
depots: object
DisplayDepotNamesListDto
Represents a set of depot access information for the user within a study, including all-depots flag and associated depot names.
-
effectiveEnd: string
(date-time)
Effective end date for user's study access (ISO8601/Z).Example:
2025-01-17T01:00:00Z -
effectiveStart: string
(date-time)
Effective start date for user's study access (ISO8601/Z).Example:
2021-01-17T01:00:00Z -
email: string
(email)
User's email address.Example:
studyuser@example.com -
firstName: string
User's first name.Example:
John -
id: string
(uuid)
Unique identifier of the user within the study.
-
lastAccess: string
(date-time)
Timestamp (ISO8601/Z) when user last accessed the study.Example:
2022-06-20T13:51:51Z -
lastName: string
User's last name.Example:
Doe -
phone: string
User's phone number.Example:
+1-222-333-4444 -
roles: array
roles
Roles assigned to the user within the study.
-
sites: object
DisplaySiteNamesListDto
Represents a set of site access information for the user within a study, including all-sites flag and associated site names.
-
userName: string
Username used for authentication.Example:
jdoe
Example:
{
"id":"7DC8B36EA5C04E1F9D11C0E5F3FFF789",
"firstName":"Jane",
"lastName":"Smith",
"userName":"jsmith",
"lastAccess":"2023-12-19T12:42:11.000Z",
"effectiveStart":"2021-06-11T10:00:00.000Z",
"effectiveEnd":"2025-09-21T10:00:00.000Z",
"roles":[
"Site User",
"Rule Designer"
],
"sites":{
"allSites":false,
"associatedSites":[
"7DC8B36EA5C04E1F9D11C0E5F3FFF780",
"6DC8B36EA5C04E1F9D11C0E5F3FFF789"
]
},
"depots":{
"allDepots":false,
"associatedDepots":[
"7DC8B36EA5W04E1F9D11C0E5F3FFF789"
]
},
"email":"studyuser@example.com",
"phone":"+1-222-333-4444"
}Nested Schema : DisplayDepotNamesListDto
Type:
objectRepresents a set of depot access information for the user within a study, including all-depots flag and associated depot names.
Show Source
-
allDepots: boolean
Flag indicating if the user has access to all depots within the study.Example:
false -
associatedDepots: array
associatedDepots
List of associated depot names for the user.
Example:
{
"allDepots":false,
"associatedDepots":[
"DepotA"
]
}Nested Schema : roles
Type:
arrayRoles assigned to the user within the study.
Show Source
-
Array of:
string
Roles assigned to the user within the study.Example:
["Rule Designer","Site User"]
Example:
[
"Rule Designer",
"Site User"
]Nested Schema : DisplaySiteNamesListDto
Type:
objectRepresents a set of site access information for the user within a study, including all-sites flag and associated site names.
Show Source
-
allSites: boolean
Flag indicating if the user has access to all sites within the study.Example:
false -
associatedSites: array
associatedSites
List of associated site names for the user.
Example:
{
"allSites":false,
"associatedSites":[
"SiteA",
"SiteB"
]
}Nested Schema : associatedDepots
Type:
arrayList of associated depot names for the user.
Show Source
-
Array of:
string
List of associated depot names for the user.Example:
["DepotA"]
Example:
[
"DepotA"
]Nested Schema : associatedSites
Type:
arrayList of associated site names for the user.
Show Source
-
Array of:
string
List of associated site names for the user.Example:
["SiteA","SiteB"]
Example:
[
"SiteA",
"SiteB"
]400 Response
Bad request
Root Schema : AuthResponse
Type:
objectGeneric API response wrapper containing result, error data, response version and status.
Show Source
-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
Result data of the API response; actual type depends on the API
-
status: string
(none)
Indicates request success ("success") or failure ("failure").Example:
success -
version: integer
(int32)
Version of the response schema.Example:
1
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: string
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.Example:
User role is missing required permission REPORTING_VIEW. Field: userId -
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectResult data of the API response; actual type depends on the API
Example:
oracle.doceng.json.BetterJsonNull@3565a0f5