listScheduledOrdersByProfile
get
/ccstore/v1/scheduledOrders/current/scheduledOrders
List Scheduled Orders By Profile. It will return the list of all the scheduled orders for the current profile. Optionally takes the X-CCOrganization header to specify current Organization context of logged in user.
Request
Supported Media Types
- application/json
Query Parameters
- limit
-
Type:
integerlimit of the scheduled orders list.- offset
Type:integerOffset of the scheduled orders list.
Response
Supported Media Types
- application/json
200 Response
Following model is returned when operation succeeds.
Body
Root Schema : listScheduledOrdersByProfile_response
- items
-
Type:
arrayitemsAdditional Properties Allowed:The array of the Scheduled orders by the profile id. - limit
-
Type:
integerThe limit results of the Scheduled orders in a page. - offset
-
Type:
integerThe offset results of the Scheduled orders. - total
-
Type:
integerThe total number of the Scheduled orders. - totalResults
-
Type:
integerThe total results of the Scheduled orders.
Nested Schema : items
Nested Schema : items
Type:
object- createDate
-
Type:
stringThe created 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 user 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 profile Id of the user of the Scheduled order. - repositoryId
-
Type:
stringThe repository Id of the user of the Scheduled order. - schedule
-
Type:
objectscheduleAdditional Properties Allowed:The schedule of the Scheduled order. - siteId
-
Type:
stringThe site Id of the user of the Scheduled order. - startDate
-
Type:
stringThe start date of the Scheduled order. - state
-
Type:
stringThe status of the Scheduled order. - templateOrder
-
Type:
objecttemplateOrderAdditional Properties Allowed:The template order of the Scheduled order. - templateOrderId
-
Type:
stringThe template order id Id of the user 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 : templateOrder
Type:
objectThe template order of the Scheduled order.
- state
-
Type:
stringThe state of the template order.
Nested Schema : daysOfWeek
Nested Schema : monthsInYear
Nested Schema : selectedDates
Nested Schema : weeksInMonth
Example application/json
{
"total":2,
"totalResults":2,
"offset":20,
"limit":10,
"items":[
{
"templateOrderId":"o10001",
"endDate":"10/01/2015",
"templateOrder":{
"state":"TEMPLATE"
},
"profileId":"user1",
"name":"testScheduleOrder",
"nextScheduledRun":"10/02/2015",
"Id":"sch001",
"state":"inactive",
"startDate":"10/01/2015"
},
{
"templateOrderId":"o10001",
"endDate":"10/01/2018",
"templateOrder":{
"state":"PENDING_APPROVAL_TEMPLATE"
},
"profileId":"user1",
"name":"testScheduleOrder",
"nextScheduledRun":"10/02/2017",
"Id":"sch002",
"state":"active",
"startDate":"10/01/2015"
},
{
"templateOrderId":"o10002",
"endDate":"10/01/2017",
"templateOrder":{
"state":"PENDING_PAYMENT_TEMPLATE"
},
"profileId":"user1",
"name":"testScheduleOrder",
"nextScheduledRun":"01/02/2017",
"Id":"sch003",
"state":"active",
"startDate":"10/01/2015"
}
]
}
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 Response Payload returned by endpoint:
{
"total": 2,
"totalResults": 2,
"offset": 20,
"limit": 10,
"items": [
{
"templateOrderId": "o10001",
"endDate": "10/01/2015",
"templateOrder": {"state": "TEMPLATE"},
"profileId": "user1",
"name": "testScheduleOrder",
"nextScheduledRun": "10/02/2015",
"Id": "sch001",
"state": "inactive",
"startDate": "10/01/2015"
},
{
"templateOrderId": "o10001",
"endDate": "10/01/2018",
"templateOrder": {"state": "PENDING_APPROVAL_TEMPLATE"},
"profileId": "user1",
"name": "testScheduleOrder",
"nextScheduledRun": "10/02/2017",
"Id": "sch002",
"state": "active",
"startDate": "10/01/2015"
},
{
"templateOrderId": "o10002",
"endDate": "10/01/2017",
"templateOrder": {"state": "PENDING_PAYMENT_TEMPLATE"},
"profileId": "user1",
"name": "testScheduleOrder",
"nextScheduledRun": "01/02/2017",
"Id": "sch003",
"state": "active",
"startDate": "10/01/2015"
}
]
}