List schedules
GET/subscriptions/schedules
Retrieves a list of all schedules.
Filtering
This endpoint supports filtering. For the general syntax, see Filtering.
The following attributes and operators are supported.
Operator | Attribute | Description |
---|---|---|
eq | external_ref | Equals. Checks if the values of two operands are equal. If they are, the condition is true. |
Request
Query Parameters
Possible values: <= 10000
The current offset by number of records, not pages. Offset is zero-based. The maximum records you can offset is 10,000. If no page size is set, the page length store setting is used.
The maximum number of records per page for this response. You can set this value up to 100. If no page size is set, the page length store setting is used.
Responses
- 200
- 400
- 500
Success. A list of schedules is returned.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
billing_run
- a billing run job.payment_run
- a payment run job.tax_run
- a tax run job.- ]
data Schedule[]
The unique identifier.
Possible values: [subscription_schedule
]
attributes ScheduleAttributesrequired
Possible values: <= 2048 characters
A unique attribute that you could use to contain information from another company system, for example. The maximum length is 2048 characters.
Possible values: >= 3 characters
and <= 1024 characters
The name of the schedule.
Possible values: <= 1024 characters
A cron-style specification of when the jobs should be created. See Schedules.
Possible values: <= 1024 characters
The location of the time zone that the schedule operates in. Subscriptions runs on Coordinated Universal Time (UTC) time and conforms to RFC 3339.
job ScheduleJobrequired
Possible values: [billing-run
, tax-run
, payment-run
, import
]
The type of job. One of the following:
The date and time a resource was updated.
The date and time a resource was created.
meta ScheduleMetarequired
The owner of a resource, either store
or organization
.
timestamps Timestampsrequired
The date and time a resource was updated.
The date and time a resource was created.
links object
{
"data": [
{
"id": "00000000-0000-0000-0000-000000000000",
"type": "subscription_schedule",
"attributes": {
"external_ref": "abc123",
"name": "Daily billing run.",
"specification": "30 0 * * *",
"location": "Europe/London",
"job": {
"job_type": "billing-run"
},
"updated_at": "2017-01-10T11:41:19.244842Z",
"created_at": "2017-01-10T11:41:19.244842Z"
},
"meta": {
"scheduled_for": "2017-07-21T17:32:28Z",
"owner": "store",
"timestamps": {
"updated_at": "2017-01-10T11:41:19.244842Z",
"created_at": "2017-01-10T11:41:19.244842Z"
}
}
}
],
"links": {}
}
Bad request. The request failed validation.
- application/json
- Schema
- Example (from schema)
- missing-name
Schema
- Array [
- ]
errors Error[]required
The HTTP response code of the error.
A brief summary of the error.
Optional additional detail about the error.
Additional supporting meta data for the error.
{
"errors": [
{
"status": 500,
"title": "Internal server error",
"detail": "An internal error has occurred.",
"meta": {
"missing_ids": [
"e7d50bd5-1833-43c0-9848-f9d325b08be8"
]
}
}
]
}
{
"errors": [
{
"title": "Validation Error",
"status": "400",
"detail": "data.attributes.name: \"name\" is required"
}
]
}
Internal server error. There was a system failure in the platform.
- application/json
- Schema
- Example (from schema)
- internal-server-error
Schema
- Array [
- ]
errors Error[]required
The HTTP response code of the error.
A brief summary of the error.
Optional additional detail about the error.
Additional supporting meta data for the error.
{
"errors": [
{
"status": 500,
"title": "Internal server error",
"detail": "An internal error has occurred.",
"meta": {
"missing_ids": [
"e7d50bd5-1833-43c0-9848-f9d325b08be8"
]
}
}
]
}
{
"errors": [
{
"title": "Internal Server Error",
"status": "500"
}
]
}