Update supply settings

put

/ec-ors-svc/rest/v10.0/studies/{studyId}/{mode}/supply/settings

Updates a study's supply settings by study ID. Rights: SupplySettingRightsPost. Required sponsor roles are: clinical supply manager and site manager. Added new fields: selectShippingAddress.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : SupplySettingsTO v10.0
Type: object
Title: SupplySettingsTO v10.0
Supply settings details object.
Show Source
Nested Schema : kitsSelectedForRandomization
Type: array
kitsSelectedForRandomization.
Show Source
Example:
[
    "30100000600000000000000000000000",
    "40100000600000000000000000000000"
]
Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : IDResponse
Type: object
Response object containing Id.
Show Source

400 Response

Invalid Kit Types OR Invalid selection of Randomize only when all kits are available
Body ()
Root Schema : ORSResponse
Type: object
Common response object.
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 Object

404 Response

Not found
Body ()
Root Schema : ORSResponse
Type: object
Common response object.
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 Object

500 Response

Internal server error
Body ()
Root Schema : ORSResponse
Type: object
Common response object.
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 Object
Back to Top