createScheduledOrder
post
/ccstore/v1/scheduledOrders
Create Scheduled Order. Create the scheduledOrder based on existing order. Optionally takes the X-CCOrganization header to specify current Organization context of logged in user.
Request
Supported Media Types
- application/json
Header Parameters
- X-CCOrganization
-
Type:
stringCurrent organization context of the logged in user
Body Parameter
Root Schema : createScheduledOrder_request
{
"schedule":{
"selectedDates":[
],
"weeksInMonth":[
1,
2,
3
],
"monthsInYear":[
1,
2
],
"daysOfWeek":[
1,
2,
3
]
},
"templateOrderId":"o0001",
"scheduleType":"calendar",
"endDate":"2017-10-01T00:00:00.000Z",
"name":"testScheduleOrder",
"startDate":"2015-10-01T00:00:00.000Z"
}
- endDate
-
Type:
stringThe end date of the Scheduled order. - name
-
Type:
stringRequired:trueThe name of the Scheduled order. - schedule
-
Type:
objectscheduleRequired:trueAdditional Properties Allowed:The schedule of the Scheduled order. - scheduleType
-
Type:
stringRequired:trueThe schedule type of the Scheduled order. - startDate
-
Type:
stringRequired:trueThe start date of the Scheduled order. - templateOrderId
-
Type:
stringRequired:trueThe template order id of the Scheduled order.
Nested Schema : schedule
Type:
objectThe schedule of the Scheduled order.
- daysOfWeek
-
Type:
arraydaysOfWeekRequired:trueAdditional Properties Allowed:The days of week of the Scheduled order. - interval
-
Type:
integerThe interval in term of number of days of the Scheduled order. - monthsInYear
-
Type:
arraymonthsInYearRequired:trueAdditional Properties Allowed:The months in year of the Scheduled order. - occurenceInDay
-
Type:
integerThe occurence in day on the Scheduled order. - selectedDates
-
Type:
arrayselectedDatesRequired:trueAdditional Properties Allowed:The selected dates in a month in year for the Scheduled order. - weeksInMonth
-
Type:
arrayweeksInMonthRequired:trueAdditional Properties Allowed:The weeks in month of the Scheduled order.
Nested Schema : daysOfWeek
Nested Schema : monthsInYear
Nested Schema : selectedDates
Nested Schema : weeksInMonth
Response
Supported Media Types
- application/json
200 Response
Following model is returned when operation succeeds.
Body
Root Schema : createScheduledOrder_response
- createDate
-
Type:
stringThe create date of the Scheduled order. - endDate
-
Type:
stringThe end date of the Scheduled order. - id
-
Type:
stringThe id of the Scheduled order. - lastScheduledRun
-
Type:
stringThe last scheduled run of the Scheduled order. - name
-
Type:
stringThe name of the Scheduled order. - nextScheduledRun
-
Type:
stringThe next scheduled run of the Scheduled order. - profileId
-
Type:
stringThe profileId of the Scheduled order. - repositoryId
-
Type:
stringThe repository Id of the Scheduled order. - schedule
-
Type:
objectscheduleAdditional Properties Allowed:The schedule of the Scheduled order. - siteId
-
Type:
stringThe siteId of the Scheduled order. - startDate
-
Type:
stringThe start date of the Scheduled order. - state
-
Type:
stringThe status of the Scheduled order. - templateOrderId
-
Type:
stringThe templateOrderId of the Scheduled order. - type
-
Type:
stringThe type of the Scheduled order. - version
-
Type:
integerThe version of the Scheduled order.
Nested Schema : schedule
Type:
objectThe schedule of the Scheduled order.
- daysOfWeek
-
Type:
arraydaysOfWeekAdditional Properties Allowed:The days of week of the Scheduled order. - interval
-
Type:
integerThe interval in term of number of days of the Scheduled order. - monthsInYear
-
Type:
arraymonthsInYearAdditional Properties Allowed:The months in year of the Scheduled order. - occurenceInDay
-
Type:
integerThe occurence in day on the Scheduled order. - selectedDates
-
Type:
arrayselectedDatesAdditional Properties Allowed:The selected dates in a month in year for the Scheduled order. - weeksInMonth
-
Type:
arrayweeksInMonthAdditional Properties Allowed:The weeks in month of the Scheduled order.
Nested Schema : daysOfWeek
Nested Schema : monthsInYear
Nested Schema : selectedDates
Nested Schema : weeksInMonth
Default Response
The error response
Body
Root Schema : errorModel
Type:
object- devMessage
-
Type:
stringAn optional non-localized message containing technical information for developers - errorCode
-
Type:
stringThe numerical code identifying the error - errors
-
Type:
arrayerrorsAdditional Properties Allowed:An optional list of errors if multiple errors were encountered - message
-
Type:
stringThe localized message describing the error - moreInfo
-
Type:
stringAn optional non-localized message with more information - o:errorPath
-
Type:
stringAn optional machine readable description of where the error occurred - status
-
Type:
stringThe HTTP status code - type
-
Type:
stringThe URI to the HTTP state code definition
Nested Schema : errors
Nested Schema : items
Type:
object- devMessage
-
Type:
stringAn optional non-localized message containing technical information for developers - errorCode
-
Type:
stringThe numerical code identifying the error - message
-
Type:
stringThe localized message describing the error - moreInfo
-
Type:
stringAn optional non-localized message with more information - o:errorPath
-
Type:
stringAn optional machine readable description of where the error occurred - status
-
Type:
stringThe HTTP status code
Examples
Sample Request:
{
"schedule": {
"selectedDates": [],
"weeksInMonth": [
1,
2,
3
],
"monthsInYear": [
1,
2
],
"daysOfWeek": [
1,
2,
3
]
},
"templateOrderId": "o0001",
"scheduleType": "calendar",
"endDate": "2017-10-01T00:00:00.000Z",
"name": "testScheduleOrder",
"startDate": "2015-10-01T00:00:00.000Z"
}