Update Task
Update a scheduled task
It’s simple to use: you only need to submit your access_key
and the payload. The API will return the scheduled task updated.
Plan Requirement
Scheduled Tasks are available only on the Scale plan. Upgrade your account via the Subscription / Dashboard section to unlock this feature.
Getting started
REST
The Task API, like all of ScreenshotMAX’s APIs, is organized around REST. It is designed to use predictable, resource-oriented URL’s and to use HTTP status codes to indicate errors.
HTTPS
The Task API requires all communications to be secured TLS 1.2 or greater.
API Versions
All of ScreenshotMAX’s APIs are versioned. The Task API is currently on Version 1.
Your Access Key
Your access key is your unique authentication key to be used to access ScreenshotMAX APIs.
To authenticate your requests, you will need to append your access key to the base URL as a query parameter for GET requests.
For POST and PATCH requests, you can include your access key in the request body as a JSON object.
You can also use the X-Access-Key
header to pass your access key.
You can find your access key in your account dashboard.
Base URL
Validation endpoint
ScreenshotMAX’s Task API simply requires your unique access key. The API will return the scheduled task updated.
This was a successful request, so the API returned a 201 OK response with the updated scheduled task.
Path parameters
Unique identifier for the scheduled task.
Body parameters
Your unique access key. You can find your access key in your account dashboard.
Name of the scheduled task. The maximum length is 100 characters.
Service to be used for the scheduled task. Available options include:
screenshot
screencast
pdf
scrape
Query parameters for the scheduled task without the access_key
parameter.
The querystring can be URL-encoded.
For example, url=https%3A%2F%2Fexample.com
is the URL-encoded version of url=https://example.com
.
Frequency of the scheduled task. Available options are:
every_minute
every_hour
every_day
every_month
custom
(use standard cron syntax)
Optional - Only available if the frequency
is set to custom
.
Cron expression used to the scheduled task. You can create one easily using Unix Cron Format
The cron expression is a string that represents a schedule in the Unix cron format. It consists of five fields separated by spaces, each representing a different unit of time. The fields are:
- minute (0-59)
- hour (0-23)
- day of the month (1-31)
- month (1-12)
- day of the week (0-6, where 0 is Sunday)
The cron expression can also include special characters such as
*
(any value),,
(list of values),-
(range of values), and/
(step values).
For example, the cron expression 34 9 28 * *
means “run at 9:34 AM on the 28th day of every month”.
Timezone for the scheduled task. Available time zones from the IANA Time Zone Database.
Indicates if the scheduled task is enabled or disabled.
Response parameters
The API response is returned in a universal and lightweight JSON format.
Unique identifier for the scheduled task. This ID is automatically generated when you create a new scheduled task.
Name of the scheduled task.
Service to be used for the scheduled task. Available options include screenshot
, screencast
, pdf
and scrape
.
Query parameters for the scheduled task without the access_key
parameter.
The querystring can be URL-encoded.
For example, url=https%3A%2F%2Fexample.com
is the URL-encoded version of url=https://example.com
.
Frequency of the scheduled task. Available options are every_minute
, every_hour
, every_day
, every_month
and custom
(use standard cron syntax).
Cron expression used to the scheduled task. Use Unix Cron Format
Timezone for the scheduled task. Available time zones from the IANA Time Zone Database.
Indicates if the scheduled task is enabled or disabled.
Unix timestamp in seconds when the scheduled task was created.
Unix timestamp in seconds when the scheduled task was last run.
Number of times the scheduled task has run.
Error Codes
Whenever you make a request that fails for some reason, an error is returned also in the JSON format. The errors include an error code and description, which you can find in detail below.
Code | Type | Details |
---|---|---|
201 | OK | The request was successful. |
400 | Bad Request | The request was rejected due to a missing or invalid parameter. |
401 | Unauthorized | The request was rejected due to an invalid access key. |
402 | Payment Required | Access denied due to an unpaid invoice. |
404 | Not Found | The requested resource was not found. |
423 | Locked | The request was denied due to insufficient quota. |
429 | Too Many Requests | The rate limit has been exceeded (too many requests per minute). |
500 | Internal server error | The request failed due to an internal server error. |