Get list of blinded lots

get

/ec-ors-svc/rest/v1.0/studies/{studyId}/{mode}/lots/blinded-lots

Retrieves list of blinded lots by study ID. Rights: LotManagementGet.

Request

Path Parameters
Query Parameters
  • Maximum number of records to display per page.
  • An order number to specify with which object you want to start retrieving result. If provided, you also need to specify a value for the limit parameter.

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : BlindedLots
Type: object
Show Source
Nested Schema : manufacturingLotIds
Type: array
Title: manufacturingLotIds
Contains manufactoring lot id.
Show Source
Nested Schema : settingsByCountry
Type: array
Show Source
Nested Schema : SettingsByCountry
Type: object
Show Source

403 Response

The study identifier does not match any study identifiers in Clinical One
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
  • details
    Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
  • 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
Nested Schema : details
Type: object
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

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
  • details
    Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
  • 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
Nested Schema : details
Type: object
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
Back to Top