Get kits from depot inventory by depot ID
get
/ec-ors-svc/rest/v1.0/studies/{studyId}/{mode}/depots/{depotId}/inventory/kits
Retrieves a list of inventories based on the filters passed in the request. Rights: ORSBlindedDepotGet, returns list of inventories at the depot for the passed filters
Request
Path Parameters
-
depotId(required): string(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical depot
-
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
-
blindedLotId: string(uuid)
blindedLotId for search
-
inventoryStatusId: array[integer]
A list of IDs of the inventory status
-
kitNumberMax: number
Minumum Kit Number for search
-
kitNumberMin: number
Minumum Kit Number for search
-
limit: integer(int32)
Maximum number of records to display per page.Default Value:
100 -
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.Default Value:
0 -
quarantineId: string
quarantineId for search
-
searchByKitNumber: string
Kit Number Search string
-
searchBySeqNumber: number
Sequence Number Search Number
-
sequenceNumberMax: number
Maximum Sequence search Number
-
sequenceNumberMin: number
Minumum Sequence search Number
-
shipmentNumber: string
shipmentNumber for search
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Successful operation
Root Schema : SiteKitDetailsResponseV1
Type:
objectTitle:
SiteKitDetailsResponseV1Contains site kit detail.
Show Source
-
blindedLotsExistsInStudy: boolean
blindedLotsExistsInStudy.Example:
true -
count: integer
(int64)
Total count of result
-
distinctInventoryStatusIds: array
distinctInventoryStatusIds
Title:
distinctInventoryStatusIdsUnique ID corresponding to each inventory status value (1 for Available, 2 for Damaged, 3 for Destroyed, 4 for Dispensed, 5 for Expired, 6 for Not in Use, 7 for Misallocated, 8 for Missing, 9 for In Transit, 10 for Quarantined, 11 for Pre-quarantined, 12 for Pending Destruction, 13 for Lost by Subject, 14 for Temporarily Unavailable, 15 for Damaged by Subject, 16 for New, 17 for Not Dispensed to Subject, 18 for Returned to Site, 19 for Conserved, 20 for Received for Destruction). -
hasMore: boolean
Attribute describes if result set has more recordsExample:
true -
kits: array
kits
Title:
kitsKit reconcile detail. -
limit: integer
(int64)
Maximum number of records to display per page.
-
links: array
links
-
offset: integer
(int64)
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.Example:
400 -
totalResults: integer
(int64)
Total number of entities in response
Nested Schema : distinctInventoryStatusIds
Type:
arrayTitle:
distinctInventoryStatusIdsUnique ID corresponding to each inventory status value (1 for Available, 2 for Damaged, 3 for Destroyed, 4 for Dispensed, 5 for Expired, 6 for Not in Use, 7 for Misallocated, 8 for Missing, 9 for In Transit, 10 for Quarantined, 11 for Pre-quarantined, 12 for Pending Destruction, 13 for Lost by Subject, 14 for Temporarily Unavailable, 15 for Damaged by Subject, 16 for New, 17 for Not Dispensed to Subject, 18 for Returned to Site, 19 for Conserved, 20 for Received for Destruction).
Allowed Values:
Show Source
[
"1",
"2",
"3",
"4",
"5",
"6",
"7",
"8",
"9",
"10",
"11",
"12",
"13",
"14",
"15",
"16",
"17",
"18",
"19",
"20"
]Example:
5,4Nested Schema : DepotUserKitReconciliationTO
Type:
Show Source
object-
barCode: string
barCodeExample:
BarCode -
blindedLotExpirationDate: string
(date-time)
Blinded lot expiration date
-
blindedLotId: string
blinded lot idExample:
B1B8327AFAA6412287106192AB5984EF -
blindedLotNumber: string
blinded lot numberExample:
blot1 -
blockNumber: string
blockNumber
-
distributionSetting: string
Allowed Values:
[ "BLINDED", "UNBLINDED" ]Distribution setting -
id: string
Inventory IdExample:
B1B8327AFAA6412287106192AB5984EF -
inventoryStatus: string
Allowed Values:
[ "Available", " Damaged", " Destroyed", " Dispensed", " Expired", " Not in Use", " Misallocated", " Missing", " In Transit", " Quarantined", " Pre-quarantined", " Pending Destruction", " Lost by Subject", " Temporarily Unavailable", " Damaged by Subject", " New", " Not Dispensed to Subject", " Returned to Site" ]Inventory statusExample:New, Damaged -
inventoryStatusId: number
(int)
Unique ID corresponding to each inventory status value (1 for Available, 2 for Damaged, 3 for Destroyed, 4 for Dispensed, 5 for Expired, 6 for Not in Use, 7 for Misallocated, 8 for Missing, 9 for In Transit, 10 for Quarantined, 11 for Pre-quarantined, 12 for Pending Destruction, 13 for Lost by Subject, 14 for Temporarily Unavailable, 15 for Damaged by Subject, 16 for New, 17 for Not Dispensed to Subject, 18 for Returned to Site, 19 for Conserved, 20 for Received for Destruction).Example:
5 -
kitDescription: string
kitDescription
-
kitNumberUTF: string
kitNumberUTFExample:
5 -
labelGroup: string
label groupExample:
labelGroup1 -
labelGroupId: string
label group idExample:
10000000000000000000000000000001 -
manufacturingLotId: string
manufacturing lot idExample:
B1B8327AFAA6412287106192AB5984EF -
manufacturingLotNumber: string
manufacture lot numberExample:
Lot1 -
quantity: number
(int)
kit quantityExample:
5 -
restrictedQuantity: number
(int)
restricted quantityExample:
1 -
sequenceNumber: number
(BigDecimal)
sequenceNumber
-
unitsPerKit: number
(BigDecimal)
unitsPerKit
Nested Schema : RelLink
Type:
objectObject contains link detail.
Show Source
-
href: string
Realtive URL
-
rel: string
link
400 Response
For invalid kit range format
Root Schema : ORSResponse
Type:
objectCommon 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 requestExample:
Success -
version: integer
(int32)
Nested Schema : ErrorResponseData
Type:
objectStructure 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
Nested Schema : result
Type:
objectResult Object
Nested Schema : details
Type:
objectDetailed 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: userId404 Response
For invalid study ID OR study still in design phase OR invalid depot ID OR invalid subject ID
Root Schema : ORSResponse
Type:
objectCommon 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 requestExample:
Success -
version: integer
(int32)
Nested Schema : ErrorResponseData
Type:
objectStructure 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
Nested Schema : result
Type:
objectResult Object
Nested Schema : details
Type:
objectDetailed 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: userId500 Response
Internal server error
Root Schema : ORSResponse
Type:
objectCommon 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 requestExample:
Success -
version: integer
(int32)
Nested Schema : ErrorResponseData
Type:
objectStructure 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
Nested Schema : result
Type:
objectResult Object
Nested Schema : details
Type:
objectDetailed 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