Create a resupply group
post
/ec-ors-svc/rest/v2.0/studies/{studyId}/{mode}/resupplies
Creates a resupply group for a study. Rights: SupplySettingRightsPost. Required sponsor roles are clinical supply manager and site manager.
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 : schema
Type:
objectRequest object for resupply group in v3.
Show Source
-
countRandomizedSubjects: boolean
Set to true to count randomized subjectsExample:
false -
groups(required): array
groups
Minimum Number of Items:
1 -
ignoreIfOutsideWindowBy: integer
(int32)
Ignore if outside window by this number of daysExample:
10 -
ignoreSubjectsOnDoseHold: boolean
Set to true to ignore subjects on dose holdExample:
false -
ignoreSubjectsOnSkipDispensingVisit: boolean
Set to true to ignore subjects on skip dispensing visitExample:
false -
resupplyId: string
(uuid)
Resupply Id
-
resupplyName(required): string
Minimum Length:
0Maximum Length:50Resupply nameExample:resupplyNameNew1 -
resupplyTypeId(required): integer
(int32)
Id of the resupply typeExample:
2 -
type(required): string
Type (Site/Depot)Example:
Site
Nested Schema : groups
Type:
arrayMinimum Number of Items:
Show Source
1-
Array of:
object ResupplyDynamicGroup
Group object for resupply group
Nested Schema : ResupplyDynamicGroup
Type:
objectGroup object for resupply group
Show Source
-
id: string
Group idExample:
32120000700000000000000000000014 -
kitTypes(required): array
kitTypes
Minimum Number of Items:
1 -
maxRange: integer
(int32)
Maximum rangeExample:
100 -
minRange: integer
(int32)
Minimum rangeExample:
0 -
name: string
Name of the dynamic groupExample:
Group 1
Nested Schema : kitTypes
Type:
arrayMinimum Number of Items:
Show Source
1-
Array of:
object ResupplyGroupRequest.KitTypeSummary
Kit type summary details object.
Nested Schema : ResupplyGroupRequest.KitTypeSummary
Type:
objectKit type summary details object.
Show Source
-
id(required): string
ID of the kit type.Example:
kitA -
initialShippingUnits: number
(double)
Minimum Value:
0Maximum Value:99The number of kits of each type that are in the initial shipment.Example:50 -
manualConsignment: number
(double)
Minimum Value:
0Maximum Value:99The number of kits of each type that are included in a manual shipment.Example:50 -
maxBuffer: number
(double)
Minimum Value:
0The number of kits that will be present at the site after a resupply shipment arrives.Example:50 -
minBuffer: number
(double)
Minimum Value:
0The number of kits that trigger a shipment when the resupply strategy runs.Example:5 -
resupplyWeeks: number
(double)
Minimum Value:
0Maximum Value:99The number of weeks that the resupply strategy resupplies for.Example:3 -
triggerWeeks: number
(double)
Minimum Value:
0Maximum Value:99The number of weeks that the resupply strategy looks out to determine the supply.Example:3
Response
Supported Media Types
- application/json
200 Response
Successful operation
400 Response
'Invalid resupply type', 'Duplicate resupply'
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: 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
Nested Schema : result
Type:
objectResult Object
500 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: 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
Nested Schema : result
Type:
objectResult Object