REST API for Clinical One Platform

Create a manual depot shipment in resupply strategy

post

/ec-ors-svc/rest/v1.0/studies/{studyId}/{mode}/resupply/depotmanual

Creates a manual depot shipment as part of a study's predictive resupply group. Rights: OrsSupplyManagerPost.

Request

Path Parameters

mode(required): string

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

ID of the study

Supported Media Types

application/json

Root Schema : ManualDepotSupplyRequest v1.0

Type: object

Title: ManualDepotSupplyRequest v1.0

Manual depot-to-depot supply request object.

Show Source

jobInstanceId: string

Job instance Id.

Example: 4FEBE3E166454E2687C6FAC306E7C86E
kits: array kits

Minimum Number of Items: 1

Maximum Number of Items: 2147483647
shippedFrom(required): string (uuid)

Source depot ID
shippedTo(required): string (uuid)

Destination depot ID

{
    "title":"ManualDepotSupplyRequest v1.0",
    "required":[
        "shippedFrom",
        "shippedTo"
    ],
    "type":"object",
    "properties":{
        "jobInstanceId":{
            "type":"string",
            "description":"Job instance Id.",
            "example":"4FEBE3E166454E2687C6FAC306E7C86E"
        },
        "kits":{
            "maxItems":2147483647,
            "minItems":1,
            "type":"array",
            "items":{
                "$ref":"#/components/schemas/DepotShipmentKitRequest"
            }
        },
        "shippedFrom":{
            "type":"string",
            "description":"Source depot ID",
            "format":"uuid"
        },
        "shippedTo":{
            "type":"string",
            "description":"Destination depot ID",
            "format":"uuid"
        }
    },
    "description":"Manual depot-to-depot supply request object."
}

Nested Schema : kits

Type: array

Minimum Number of Items: 1

Maximum Number of Items: 2147483647

Show Source

Array of: object DepotShipmentKitRequest

Contains kit details for depot shipment creation.

{
    "maxItems":2147483647,
    "minItems":1,
    "type":"array",
    "items":{
        "$ref":"#/components/schemas/DepotShipmentKitRequest"
    }
}

Nested Schema : DepotShipmentKitRequest

Type: object

Contains kit details for depot shipment creation.

Show Source

kitTypeId: string (uuid)

ID of the kit type.
quantity: string

Kit quantity

Example: 2

{
    "type":"object",
    "properties":{
        "kitTypeId":{
            "type":"string",
            "description":"ID of the kit type.",
            "format":"uuid"
        },
        "quantity":{
            "type":"string",
            "description":"Kit quantity",
            "example":"2"
        }
    },
    "description":"Contains kit details for depot shipment creation."
}

Response

Supported Media Types

application/json

200 Response

Successful operation

404 Response

Not found

Root 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."
}

500 Response

Internal server error

Root 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."
}