Jump to

• Request
• Response

Get manufacturing lot by ID

get

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

Retrieves manufacturing lot by lot ID. Rights: LotManagementGet.

Request

Path Parameters

• id(required): string
  ID of the lot
• 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.

Query Parameters

• includeDeleted: boolean

There's no request body for this operation.

Back to Top

Response

Supported Media Types

• application/json

200 Response

Successful operation

Body ()

Root Schema : ManufacturingLotTO v2.0

Type: object

Title: ManufacturingLotTO v2.0

Manufacturing Lot details

Show Source

• blindedLotId: string (uuid)
  Title: Blinded Lot ID

  Blinded lot id
• blindedLotVersionStart: string (date-time)
  Blinded lot version start date
• comment: string
  Comment.

  Example: Some comment
• doNotCount: number (BigDecimal)
  Title: Do Not Count

  Do not count(DNC) days

  Example: 10
• doNotShip: number (BigDecimal)
  Title: Do Not Ship

  Do not ship(DNS) days

  Example: 10
• expirationDate: string (date-time)
  Title: Expiration Date

  Expiration date
• inUse: boolean
  Indicates if lot is in use

  Example: true
• lotId: string (uuid)
  Title: Lot ID

  Lot id
• lotNumber: string
  Title: Lot Number

  Lot number

  Example: Lot1001
• manufacturingLotNumber: string
  Title: Manufacturing Lot Number

  Manufacturing lot number

  Example: Mlot1001
• 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
• runNumber: string
  Run number

  Example: run number 01
• softwareVersionNumber: number (double)
  Software version number.

  Example: 2
• 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.

{
    "title":"ManufacturingLotTO v2.0",
    "type":"object",
    "properties":{
        "manufacturingLotNumber":{
            "title":"Manufacturing Lot Number",
            "type":"string",
            "description":"Manufacturing lot number",
            "example":"Mlot1001"
        },
        "expirationDate":{
            "title":"Expiration Date",
            "type":"string",
            "description":"Expiration date",
            "format":"date-time"
        },
        "blindedLotId":{
            "title":"Blinded Lot ID",
            "type":"string",
            "description":"Blinded lot id",
            "format":"uuid"
        },
        "doNotCount":{
            "title":"Do Not Count",
            "type":"number",
            "description":"Do not count(DNC) days",
            "format":"BigDecimal",
            "example":10
        },
        "doNotShip":{
            "title":"Do Not Ship",
            "type":"number",
            "description":"Do not ship(DNS) days",
            "format":"BigDecimal",
            "example":10
        },
        "lotNumber":{
            "title":"Lot Number",
            "type":"string",
            "description":"Lot number",
            "example":"Lot1001"
        },
        "versionStart":{
            "type":"string",
            "description":"The timestamp marking the beginning of the validity period for this record version within the system.",
            "format":"date-time"
        },
        "userId":{
            "type":"string",
            "description":"User ID",
            "format":"uuid"
        },
        "runNumber":{
            "type":"string",
            "description":"Run number",
            "example":"run number 01"
        },
        "inUse":{
            "type":"boolean",
            "description":"Indicates if lot is in use",
            "example":true
        },
        "versionEnd":{
            "type":"string",
            "description":"The end date until which the data is applicable or valid.",
            "format":"date-time"
        },
        "blindedLotVersionStart":{
            "type":"string",
            "description":"Blinded lot version start date",
            "format":"date-time"
        },
        "operationType":{
            "type":"string",
            "description":"Operation type.",
            "example":"MODIFIED",
            "enum":[
                "CREATED",
                "REMOVED",
                "MODIFIED"
            ]
        },
        "objectVersionNumber":{
            "type":"number",
            "description":"Object version number.",
            "format":"double",
            "example":5
        },
        "softwareVersionNumber":{
            "type":"number",
            "description":"Software version number.",
            "format":"double",
            "example":2
        },
        "reason":{
            "type":"string",
            "description":"Reason.",
            "example":"Some reason"
        },
        "comment":{
            "type":"string",
            "description":"Comment.",
            "example":"Some comment"
        },
        "lotId":{
            "title":"Lot ID",
            "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

Body ()

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

{
    "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":"object",
            "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

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

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

{
    "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":"object",
            "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

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