Create or update selected depot resupply associations
put
/ec-ors-svc/rest/v1.0/studies/{studyId}/{mode}/depot/resupplies/updateselected
Creates or updates selected associations between a resupply and a depot.
Rights: SupplySettingRightsPost.
Required sponsor roles are clinical supply manager and depot manager.
Rights: SupplySettingRightsPost.
Required sponsor roles are clinical supply manager and depot manager.
Request
Path Parameters
-
mode(required): string
Mode of the study, accepts: test, active, or training.
-
studyId(required): string(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
array-
Array of:
object DepotResupplyRequest
Depot resupply request object.
Nested Schema : DepotResupplyRequest
Type:
objectDepot resupply request object.
Show Source
-
depotId: string
Example:
B1B8327AFAA6412287106192AB5984EF -
resupplyId: string
Example:
B1B8327AFAA6412287106192AB5984EF
Response
Supported Media Types
- application/json
200 Response
Successful operation
Nested Schema : SiteResupply
Type:
objectSite resupply details.
Show Source
-
comment: string
CommentsExample:
Some comments -
id: string
(uuid)
Resupply site id
-
objectVersionNumber: number
(double)
Object Version Number.Example:
5 -
operationType: string
Allowed Values:
[ "CREATED", "REMOVED", "MODIFIED" ]Operation type.Example:MODIFIED -
reason: string
Reason.Example:
Some reason -
resupplyId: string
(uuid)
Resupply ID
-
resupplyVersionStart: string
(date-time)
Resupply version start
-
siteId: string
(uuid)
Site ID
-
siteVersionStart: string
(date-time)
Site version start
-
softwareVersionNumber: number
(double)
Software Version Number.Example:
2 -
subjectVisitId: string
(uuid)
-
userId: string
(uuid)
User id
-
versionEnd: string
(date-time)
The end date until which the data is applicable or valid.
-
versionStart: string
(date-time)
The timestamp marking the beginning of the validity period for this record version within the system.
400 Response
'Depot in the study does not match the Clinical One study configuration', 'Duplicate depot'
Root Schema : ORSResponse
Type:
objectCommon response object.
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 Object
-
status: string
Status of requestExample:
Success -
version: integer
(int32)
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: object
details
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
-
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 Object
Nested Schema : details
Type:
objectDetailed 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: userId404 Response
'Resupply not found', 'Study identifier does not match any study identifiers in Clinical One.'
Root Schema : ORSResponse
Type:
objectCommon response object.
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 Object
-
status: string
Status of requestExample:
Success -
version: integer
(int32)
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: object
details
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
-
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 Object
Nested Schema : details
Type:
objectDetailed 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: userId500 Response
Internal server error
Root Schema : ORSResponse
Type:
objectCommon response object.
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 Object
-
status: string
Status of requestExample:
Success -
version: integer
(int32)
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: object
details
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
-
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 Object
Nested Schema : details
Type:
objectDetailed 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