[Deprecated]: Get orders

get

/ec-ors-svc/rest/v4.0/studies/{studyId}/{mode}/orders

Deprecated: Retrieves a list of all orders in a study. If a kit list is disabled, the shipment will be excluded from the Orders API. Rights: OrsInventoryGet, OrsUnblinded.

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 : OrderInventoryPagedListResponse v4.0
Type: object
Title: OrderInventoryPagedListResponse v4.0
Contains order details for the inventory.
Show Source
Nested Schema : resultData
Type: array
Show Source
Nested Schema : shipments
Type: array
Show Source
Nested Schema : OrderInventoryDTO v4.0
Type: object
Title: OrderInventoryDTO v4.0
Contains inventory order details.
Show Source
Nested Schema : inventory
Type: array
Show Source
Nested Schema : OrderDTO v3.0
Type: object
Title: OrderDTO v3.0
Contains order related details.
Show Source
Nested Schema : InventoryDTO v2.0
Type: object
Title: InventoryDTO v2.0
Contains kit details.
Show Source

400 Response

Invalid order status value
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
  • 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
Result 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