REST API for Clinical One Platform

Get all manufacturing lots

get

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

Retrieves all manufacturing lots by study ID. Rights: LotManagementGet.

Request

Path Parameters

mode(required): string

Mode of the study, accepts: test, active, or training
studyId(required): string(uuid)

ID of the study

Query Parameters

limit: integer(int32)

Maximum number of records to display per page.
offset: integer(int32)

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. Offset is affected by the value of the order parameter

There's no request body for this operation.

Response

Supported Media Types

application/json

200 Response

Successful operation

Root Schema : schema

Type: array

Show Source

Array of: object ManufacturingLotTO v1.0

Title: ManufacturingLotTO v1.0

Manufacturing Lot details

{
    "type":"array",
    "items":{
        "$ref":"#/components/schemas/ManufacturingLotTOV1"
    }
}

Nested Schema : ManufacturingLotTO v1.0

Type: object

Title: ManufacturingLotTO v1.0

Manufacturing Lot details

Show Source

blindedLotId: string (uuid)

Blinded lot id
doNotCount: number (BigDecimal)

Do not count(DNC) days

Example: 10
doNotShip: number (BigDecimal)

Do not ship(DNS) days

Example: 10
expirationDate: string (date-time)

Expiration date
lotId: string (uuid)

Lot id
lotNumber: string

Lot number

Example: Lot1001
manufacturingLotNumber: string

Manufacturing lot number

Example: Mlot1001

{
    "title":"ManufacturingLotTO v1.0",
    "type":"object",
    "properties":{
        "manufacturingLotNumber":{
            "type":"string",
            "description":"Manufacturing lot number",
            "example":"Mlot1001"
        },
        "expirationDate":{
            "type":"string",
            "description":"Expiration date",
            "format":"date-time"
        },
        "blindedLotId":{
            "type":"string",
            "description":"Blinded lot id",
            "format":"uuid"
        },
        "doNotCount":{
            "type":"number",
            "description":"Do not count(DNC) days",
            "format":"BigDecimal",
            "example":10
        },
        "doNotShip":{
            "type":"number",
            "description":"Do not ship(DNS) days",
            "format":"BigDecimal",
            "example":10
        },
        "lotNumber":{
            "type":"string",
            "description":"Lot number",
            "example":"Lot1001"
        },
        "lotId":{
            "type":"string",
            "description":"Lot id",
            "format":"uuid"
        }
    },
    "description":"Manufacturing Lot details"
}

403 Response

The study identifier does not match any study identifiers in Clinical One

Root Schema : ORSResponse

Type: object

Common 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 request

Example: Success
version: integer (int32)

{
    "type":"object",
    "properties":{
        "status":{
            "type":"string",
            "description":"Status of request",
            "example":"Success"
        },
        "result":{
            "type":"object",
            "description":"Result Object"
        },
        "errorData":{
            "$ref":"#/components/schemas/ErrorResponseData"
        },
        "version":{
            "type":"integer",
            "format":"int32"
        }
    },
    "description":"Common response object."
}

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: 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

{
    "type":"object",
    "properties":{
        "errorCode":{
            "type":"string",
            "description":"Application or business-specific error code representing the error type.",
            "example":"REPT_401"
        },
        "errorMessage":{
            "type":"string",
            "description":"Human-readable error message describing the failure or issue.",
            "example":"Unauthorized: User does not have access to the requested resource"
        },
        "details":{
            "type":"string",
            "description":"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"
        }
    },
    "description":"Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details."
}

Nested Schema : result

Type: object

Result Object

500 Response

Internal server error

Root Schema : ORSResponse

Type: object

Common 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 request

Example: Success
version: integer (int32)

{
    "type":"object",
    "properties":{
        "status":{
            "type":"string",
            "description":"Status of request",
            "example":"Success"
        },
        "result":{
            "type":"object",
            "description":"Result Object"
        },
        "errorData":{
            "$ref":"#/components/schemas/ErrorResponseData"
        },
        "version":{
            "type":"integer",
            "format":"int32"
        }
    },
    "description":"Common response object."
}

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: 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

{
    "type":"object",
    "properties":{
        "errorCode":{
            "type":"string",
            "description":"Application or business-specific error code representing the error type.",
            "example":"REPT_401"
        },
        "errorMessage":{
            "type":"string",
            "description":"Human-readable error message describing the failure or issue.",
            "example":"Unauthorized: User does not have access to the requested resource"
        },
        "details":{
            "type":"string",
            "description":"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"
        }
    },
    "description":"Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details."
}

Nested Schema : result

Type: object

Result Object