Get requested active users for a study with study roles and email address
post
/ec-auth-svc/rest/v1.0/authstudies/{StudyID}/users
Retrieves all the requested users that belong to a study and mode.
Request
Path Parameters
-
StudyID(required): string(uuid)
Study IDExample:
ABE31741A0E945F6B827048B279F2F19
Query Parameters
-
mode: string
Mode of the study. Accepts active, test, or trainingAllowed Values:
[ "design", "test", "training", "active", "all" ]Example:design
Supported Media Types
- */*
Root Schema : schema
Type:
objectPayload listing userIds for which study roles are to be fetched.
Show Source
-
userIds: array
userIds
List of user IDs for which roles or study access is requested.
Example:
{
"userIds":[
"11223344AABBCCDD11223344AABBCCDD",
"FFEEDDCCBBAA99887766554433221100"
]
}Nested Schema : userIds
Type:
arrayList of user IDs for which roles or study access is requested.
Show Source
-
Array of:
string(uuid)
List of user IDs for which roles or study access is requested.
Example:
[
"11223344AABBCCDD11223344AABBCCDD",
"FFEEDDCCBBAA99887766554433221100"
]Response
Supported Media Types
- application/json
200 Response
Success
Nested Schema : users
Type:
Show Source
array-
Array of:
object DisplayStudyUserStudyRolesDto v1.0
Title:
DisplayStudyUserStudyRolesDto v1.0Authorized User Info
Nested Schema : DisplayStudyUserStudyRolesDto v1.0
Type:
objectTitle:
DisplayStudyUserStudyRolesDto v1.0Authorized User Info
Show Source
Nested Schema : studyRole
Type:
Show Source
array-
Array of:
object DisplayStudyRoleDtoV2
Single study role assignment in a mode. Includes primary ID, display label, and version validity dates (inherited from DisplayAuthBaseDto).
Nested Schema : DisplayStudyRoleDtoV2
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"
}
]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