Get all users for a study
get
/ec-auth-svc/rest/v1.0/authstudies/{StudyID}/paginatedUsers
Retrieve a paginated list of user assignments for a given study. Results can be filtered using search string, sorted, and paginated.
Request
Path Parameters
-
StudyID(required): string
Study unique identifier.Example:
9F5087A6C75E4A27AF1CA8B5F24D5992
Query Parameters
-
firstResult: integer(int32)
Index of the first user returned in this page.Example:
0 -
includeRemoved: string
Include removed users? "Y" for yes, "N" for no.Default Value:
NExample:N -
limit: string
Pagination limit (page size).Default Value:
10Example:20 -
offset: string
Offset index for pagination.Default Value:
0Example:0 -
rowsToReturn: integer(int32)
Number of users to return in this page.Example:
10 -
searchString: string
Search filter for users.Example:
John Smith -
sortBy: array[string]
List of fields to sort by.Example:
[ "userName", "lastName" ] -
viewMode: string
Optional study mode for filtering (e.g., design).Example:
design
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
List of user assignments for the study returned successfully.
Root Schema : DisplayStudyUserListDtoV3
Type:
objectPaginated and detailed response object representing a list of study users, including overall count and returned slice, for API v4 and similar endpoints. Each user entry is deeply expanded, including all modes, role assignments, sites, and depots, as required by downstream consumers.
Show Source
-
firstUserReturned: integer
(int32)
Index of the first user returned in this page (1-based).Example:
1 -
users: object
users
Full representation of a user returned in the study-users APIs. Covers all identifiers, contact, temporal, and role/mode/assignment details. See the 'modes' property for full expansion of all site/role/depot assignments.
-
usersFound: integer
(int32)
Total count of users matching the filter or query.Example:
2 -
usersReturned: integer
(int32)
Count of user entries included in this result slice.Example:
2
Nested Schema : users
Type:
objectFull representation of a user returned in the study-users APIs. Covers all identifiers, contact, temporal, and role/mode/assignment details. See the 'modes' property for full expansion of all site/role/depot assignments.
Show Source
-
effectiveEnd: string
(date-time)
Effective end date for the user's study assignment (ISO 8601).Example:
2024-05-31T23:59:59Z -
effectiveStart: string
(date-time)
Effective start date for the user's study assignment (ISO 8601).Example:
2021-06-01T00:00:00Z -
email: string
Primary email address for the user.Example:
priya.sundaram@examplemail.com -
firstName: string
First name of the user.Example:
Priya -
id: string
(uuid)
User's unique ID.
-
lastAccess: string
(date-time)
Date and time of user's last access (ISO 8601).Example:
2023-08-08T12:00:00Z -
lastName: string
Last name of the user.Example:
Sundaram -
modes: object
modes
All assignment information for a user in a given mode (e.g., active, training) including roles, study roles, mapped sites and mapped depots. This object is a key part of user-level responses.
-
phone: string
Phone or contact information for the user.Example:
+1-404-505-6060 -
userName: string
Login username for the user.Example:
psundaram
Example:
[
{
"id":"B29BC40C838C42C5972D35880BEBB403",
"firstName":"Alice",
"lastName":"Lee",
"userName":"alice.lee",
"email":"alice.lee@fakemail.org",
"phone":"+1-101-202-3030",
"lastAccess":"2024-02-14T18:00:00.000Z",
"effectiveStart":"2023-01-01T00:00:00.000Z",
"effectiveEnd":"2025-12-31T23:59:59.000Z",
"modes":[
{
"modeName":"active",
"roles":[
{
"id":"AABBCCDDEEFF112233445566778899AA",
"roleName":"Site Coordinator"
}
],
"studyRole":[
{
"id":"D0F1E2C3B4A5968775CCEE8855229966",
"studyRoleName":"Monitor",
"versionStart":"2021-01-01T00:00:00.000Z",
"versionEnd":"2024-12-31T23:59:59.000Z"
}
],
"sites":{
"allSites":false,
"siteIds":[
"817F1E2B3D4C5678A1928833BFA40721"
]
},
"depots":{
"allDepots":false,
"names":[
"DepotZ"
]
}
}
]
}
]Nested Schema : modes
Type:
objectAll assignment information for a user in a given mode (e.g., active, training) including roles, study roles, mapped sites and mapped depots. This object is a key part of user-level responses.
Show Source
-
depots: object
DisplayDepotsListDtoV2
Collection representing the set of depots mapped for a user/mode. Includes global/all flag and list of detailed depot associations.
-
modeName: string
Study mode for these assignments (e.g., active, training, etc.)Example:
active -
roles: object
roles
User role assignment within a study mode. Contains role reference, display label, and (if set) a mapped StudyRoleID. UUIDs are always uppercase.
-
sites: object
DisplaySitesListDtoV2
Collection representing the set of sites mapped for a user/mode. Includes global/all flag and list of detailed site associations.
-
studyRole: object
studyRole
Single study role assignment in a mode. Includes primary ID, display label, and version validity dates (inherited from DisplayAuthBaseDto).
Example:
[
{
"modeName":"active",
"roles":[
{
"id":"F0DEEFCB66A14C2AA0699165055A38C1",
"roleName":"Data Manager"
}
],
"studyRole":[
{
"id":"1A9CF1A460CD440CA62B6F9EA258F968",
"studyRoleName":"Investigator",
"versionStart":"2021-07-01T00:00:00.000Z",
"versionEnd":"2024-01-31T23:59:59.000Z"
}
],
"sites":{
"allSites":false,
"siteIds":[
"21F6B67B398A4977A19964FF7B7A68FD"
]
},
"depots":{
"allDepots":true,
"names":[
]
}
}
]Nested Schema : DisplayDepotsListDtoV2
Type:
objectCollection representing the set of depots mapped for a user/mode. Includes global/all flag and list of detailed depot associations.
Show Source
-
allDepots: boolean
Global depot mapping: if true, all depots are assigned to this user/mode.Example:
true -
associatedDepots: object
associatedDepots
Represents a single depot facility mapped to the user/mode assignment. UUID is always uppercase.
-
versionEnd: string
(date-time)
End date for the object's version validity. ISO 8601 format.Example:
2025-06-17T10:15:30Z -
versionStart: string
(date-time)
Start date for the object's version validity. ISO 8601 format.Example:
2020-06-17T10:15:30Z
Example:
{
"allDepots":true,
"names":[
]
}Nested Schema : roles
Type:
objectUser role assignment within a study mode. Contains role reference, display label, and (if set) a mapped StudyRoleID. UUIDs are always uppercase.
Show Source
-
id: string
Unique role IDExample:
F0DEEFCB66A14C2AA0699165055A38C1 -
roleName: string
Display name for this application or system role.Example:
Data Manager -
StudyRoleID: string
If present, the mapped StudyRoleID for this user/type.Example:
23FF2AE2F25746B993190A489ED09727 -
versionEnd: string
(date-time)
End date for the object's version validity. ISO 8601 format.Example:
2025-06-17T10:15:30Z -
versionStart: string
(date-time)
Start date for the object's version validity. ISO 8601 format.Example:
2020-06-17T10:15:30Z
Example:
[
{
"id":"F0DEEFCB66A14C2AA0699165055A38C1",
"roleName":"Data Manager"
}
]Nested Schema : DisplaySitesListDtoV2
Type:
objectCollection representing the set of sites mapped for a user/mode. Includes global/all flag and list of detailed site associations.
Show Source
-
allSites: boolean
Global site mapping: if true, all sites are assigned to this user/mode.Example:
false -
associatedSites: object
associatedSites
Represents a single site mapped to user/mode assignments. UUID is always uppercase.
-
versionEnd: string
(date-time)
End date for the object's version validity. ISO 8601 format.Example:
2025-06-17T10:15:30Z -
versionStart: string
(date-time)
Start date for the object's version validity. ISO 8601 format.Example:
2020-06-17T10:15:30Z
Example:
{
"allSites":false,
"siteIds":[
"21F6B67B398A4977A19964FF7B7A68FD"
]
}Nested Schema : studyRole
Type:
objectSingle study role assignment in a mode. Includes primary ID, display label, and version validity dates (inherited from DisplayAuthBaseDto).
Show Source
-
id: string
(uuid)
Unique study role ID (32-character uppercase hexadecimal UUID).
-
roleName: string
-
versionEnd: string
(date-time)
End date for the object's version validity. ISO 8601 format.Example:
2025-06-17T10:15:30Z -
versionStart: string
(date-time)
Start date for the object's version validity. ISO 8601 format.Example:
2020-06-17T10:15:30Z
Example:
[
{
"id":"1A9CF1A460CD440CA62B6F9EA258F968",
"studyRoleName":"Investigator",
"versionStart":"2021-07-01T00:00:00.000Z",
"versionEnd":"2024-01-31T23:59:59.000Z"
}
]Nested Schema : associatedDepots
Type:
objectRepresents a single depot facility mapped to the user/mode assignment. UUID is always uppercase.
Show Source
-
depotName: string
Name/label for the assigned depot.Example:
VaultDepot1 -
id: string
(uuid)
Depot unique identifier (32-character uppercase hexadecimal UUID).
-
roleName: string
-
versionEnd: string
(date-time)
End date for the object's version validity. ISO 8601 format.Example:
2025-06-17T10:15:30Z -
versionStart: string
(date-time)
Start date for the object's version validity. ISO 8601 format.Example:
2020-06-17T10:15:30Z
Example:
[
{
"depotId":"7A01356CE45847A0B2B4E5D7DDA18942",
"name":"Vault"
}
]Nested Schema : associatedSites
Type:
objectRepresents a single site mapped to user/mode assignments. UUID is always uppercase.
Show Source
-
id: string
(uuid)
Site unique identifier (32-character uppercase hexadecimal UUID).
-
roleName: string
-
siteName: string
Human-readable name for the assigned site.Example:
Site123 -
versionEnd: string
(date-time)
End date for the object's version validity. ISO 8601 format.Example:
2025-06-17T10:15:30Z -
versionStart: string
(date-time)
Start date for the object's version validity. ISO 8601 format.Example:
2020-06-17T10:15:30Z
Example:
[
{
"siteId":"2BC6B6F87E774B24A20C769C2B80B7F5",
"name":"SiteA"
}
]Examples
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