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
-
StudyID(required): string(uuid)
Unique identifier for the study.Example:
85EFD8B9FF11437F8D0DA3F314A9D123
Supported Media Types
- application/json
Root Schema : schema
Type:
objectRequest 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
-
allUsers: boolean
Flag indicating if operation should apply to all users found by userSearchSpecs. If true, all users matching the search will be updated; otherwise, only those explicitly listed in userIds.Example:
false -
effectiveEnd: string
(date-time)
Effective end date/time to set (in ISO 8601 format).Example:
2024-12-31T23:59:59Z -
effectiveStart: string
(date-time)
Effective start date/time to set (in ISO 8601 format).Example:
2023-01-01T00:00:00Z -
userIds: array
userIds
List of user IDs to update (if bulk selection not by query)
-
userSearchSpecs: object
UsersSearchSpecificationsDto
Search/filter specifications for selecting users during bulk role/effective/site updates.
Nested Schema : userIds
Type:
arrayList of user IDs to update (if bulk selection not by query)
Show Source
-
Array of:
string(uuid)
List of user IDs to update (if bulk selection not by query)
Example:
[
"1BC29B36F5D64B1B95F4BDBBCEA481BE",
"2ABC8A2C11045A584ADEA8760F72B114"
]Nested Schema : UsersSearchSpecificationsDto
Type:
objectSearch/filter specifications for selecting users during bulk role/effective/site updates.
Show Source
-
depots: object
depots
Depots data to filter the users
-
mode: string
Study mode for the searchExample:
active -
searchString: string
Free text to search/filter usersExample:
site, US -
sites: object
sites
Sites data to filter the users
-
sortBy: string
Result sort columnExample:
lastName -
sortOrder: string
Sort order, ascending/descendingExample:
asc -
studyRoles: array
studyRoles
List of study role UUIDs
-
studyRoleTypes: array
studyRoleTypes
List of study role types
-
userStatus: string
User status for filteringExample:
Inactive
Nested Schema : depots
Type:
objectDepots data to filter the users
Show Source
Example:
{
"names":[
"DepotA"
]
}Nested Schema : sites
Type:
objectSites data to filter the users
Show Source
Example:
{
"ids":[
"123F0B1426C11EE90C31234567890AAA"
]
}Nested Schema : studyRoles
Type:
arrayList of study role UUIDs
Show Source
-
Array of:
string(uuid)
List of study role UUIDs
Example:
[
"AF73A2EEA90B4E9394CE6CB40B5BC66E"
]Nested Schema : studyRoleTypes
Type:
arrayList of study role types
Show Source
-
Array of:
string
List of study role typesExample:
["PrincipalInvestigator"]
Example:
[
"PrincipalInvestigator"
]Examples
Back to Top
Response
Supported Media Types
- application/json
204 Response
Success
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@3565a0f5500 Response
Error
Root 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