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
Query Parameters
  • Mode of the study. Accepts active, test, or training
    Allowed Values: [ "design", "test", "training", "active", "all" ]
    Example:
    design
Supported Media Types
Request Body - */* ()
Root Schema : schema
Type: object
Payload listing userIds for which study roles are to be fetched.
Show Source
Example:
{
    "userIds":[
        "11223344AABBCCDD11223344AABBCCDD",
        "FFEEDDCCBBAA99887766554433221100"
    ]
}
Nested Schema : userIds
Type: array
List of user IDs for which roles or study access is requested.
Show Source
Example:
[
    "11223344AABBCCDD11223344AABBCCDD",
    "FFEEDDCCBBAA99887766554433221100"
]
Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : DisplayStudyUserStudyRolesListDto
Type: object
Show Source
Nested Schema : users
Type: array
Show Source
Nested Schema : DisplayStudyUserStudyRolesDto v1.0
Type: object
Title: DisplayStudyUserStudyRolesDto v1.0
Authorized User Info
Show Source
Nested Schema : studyRole
Type: array
Show Source
Nested Schema : DisplayStudyRoleDtoV2
Type: object
Single study role assignment in a mode. Includes primary ID, display label, and version validity dates (inherited from DisplayAuthBaseDto).
Show Source
Example:
[
    {
        "id":"1A9CF1A460CD440CA62B6F9EA258F968",
        "studyRoleName":"Investigator",
        "versionStart":"2021-07-01T00:00:00.000Z",
        "versionEnd":"2024-01-31T23:59:59.000Z"
    }
]

400 Response

Bad request
Body ()
Root Schema : AuthResponse
Type: object
Generic API response wrapper containing result, error data, response version and status.
Show Source
Nested Schema : ErrorResponseData
Type: object
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
  • 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
  • Application or business-specific error code representing the error type.
    Example: REPT_401
  • Human-readable error message describing the failure or issue.
    Example: Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type: object
Result data of the API response; actual type depends on the API
Example:
oracle.doceng.json.BetterJsonNull@3565a0f5
Back to Top