Get user roles in a study

get

/ec-auth-svc/rest/v1.0/authstudies/{StudyID}/userroles

Retrieve all user roles assigned for the given study.

Request

Path Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

User roles by category, with each role fully expanded, as per schema and including all fields.
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : DisplayStudyUserRolesDto
Type: object
Describes user roles within a study, indicating the type/category and a list of role objects assigned (typically study role details).
Show Source
  • roles
    List of role objects (actual schema depends on the use context, typically a DTO representing role details).
  • Type or category of the role for the user within a study (such as INVESTIGATOR, VIEWER, etc).
    Example: design
Example:
{
  "roleType": "design",
  "roles": [
    {
      "roleId": "D0F183DC273340CEA7AFDCB93A5B3D4B",
      "roleName": "Assign Site to a Study",
    },
    {
      "roleId": "9ED1AE19B0B04188B8A70A8D8374F315",
      "roleName": "View Library Objects",
    }
  ]
}
Nested Schema : roles
Type: array
List of role objects (actual schema depends on the use context, typically a DTO representing role details).
Show Source
  • items
    List of role objects (actual schema depends on the use context, typically a DTO representing role details).
Example:
[
    {
        "roleId":"D0F183DC273340CEA7AFDCB93A5B3D4B",
        "roleName":"Assign Site to a Study"
    },
    {
        "roleId":"9ED1AE19B0B04188B8A70A8D8374F315",
        "roleName":"View Library Objects"
    }
]
Nested Schema : items
Type: object
List of role objects (actual schema depends on the use context, typically a DTO representing role details).
Example:
[
    {
        "roleId":"D0F183DC273340CEA7AFDCB93A5B3D4B",
        "roleName":"Assign Site to a Study"
    },
    {
        "roleId":"9ED1AE19B0B04188B8A70A8D8374F315",
        "roleName":"View Library Objects"
    }
]
Examples

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