Get kit details by order

get

/ec-ors-svc/rest/v4.0/studies/{studyId}/{mode}/shipments/{shipmentId}/kits

Retrieves a kit's details by order. Rights: OrsInventoryGet, OrsUnblinded. Added new field: kitNumberUTF to the response

Request

Path Parameters
Query Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : ShipmentKitsResponse v4.0
Type: object
Title: ShipmentKitsResponse v4.0
Response object containing shipment kits details.
Show Source
Nested Schema : kitTypes
Type: array
Show Source
Nested Schema : ShipmentKitsResponse.KitTypeSummary v4.0
Type: object
Title: ShipmentKitsResponse.KitTypeSummary v4.0
Kit type summary details object.
Show Source
Nested Schema : kits
Type: array
Show Source
Nested Schema : nsKits
Type: array
Show Source
Nested Schema : ShipmentKitsResponse.Kit v5.0
Type: object
Title: ShipmentKitsResponse.Kit v5.0
Kit details object.
Show Source
Nested Schema : ShipmentKitsResponse.NonSerialized v5.0
Type: object
Title: ShipmentKitsResponse.NonSerialized v5.0
Kit details object.
Show Source

404 Response

'Invalid study ID', 'Study still in design phase' or 'Invalid shipment ID'
Body ()
Root Schema : DesignerResponse
Type: 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

500 Response

Internal server error
Body ()
Root Schema : DesignerResponse
Type: 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
Back to Top