Bulk user effective dates update

put

/ec-auth-svc/rest/v1.0/authusers/studies/{StudyID}/users/effectivedates

Bulk update effective start/end dates for user assignments in a study. Provide a list of user IDs or filter criteria, plus new effective dates, in the request body.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Request payload for performing bulk update of effective start/end dates for a set of users in a study. Selection of users may be done by explicit userId, allUsers, or the userSearchSpecs criteria. All date-times use ISO 8601 string format.
Show Source
Nested Schema : userIds
Type: array
List of user IDs to update (if bulk selection not by query)
Show Source
Example:
[
    "1BC29B36F5D64B1B95F4BDBBCEA481BE",
    "2ABC8A2C11045A584ADEA8760F72B114"
]
Nested Schema : UsersSearchSpecificationsDto
Type: object
Search/filter specifications for selecting users during bulk role/effective/site updates.
Show Source
Nested Schema : depots
Type: object
Depots data to filter the users
Show Source
Example:
{
    "names":[
        "DepotA"
    ]
}
Nested Schema : sites
Type: object
Sites data to filter the users
Show Source
Example:
{
    "ids":[
        "123F0B1426C11EE90C31234567890AAA"
    ]
}
Nested Schema : studyRoles
Type: array
List of study role UUIDs
Show Source
Example:
[
    "AF73A2EEA90B4E9394CE6CB40B5BC66E"
]
Nested Schema : studyRoleTypes
Type: array
List of study role types
Show Source
Example:
[
    "PrincipalInvestigator"
]
Nested Schema : depotIds
Type: array
Show Source
Nested Schema : siteIds
Type: array
Show Source
Examples

Back to Top

Response

Supported Media Types

204 Response

Success

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

500 Response

Error
Body ()
Root 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
Back to Top