Cron job monitor

get
Pulse

https://api.cronly.app/1.1/cron/pulse
You can send a pulse request each time your cron job runs successfully. This call should be called at the end of your cron job.
Request
Response
Request
Query Parameters
token
required
string
Your cron job monitor token
Response
200: OK
Each cron job monitor can have one of the following statuses. new Cronly is waiting for the first pulse. running Your cron is due. Cronly is waiting for your pulse. healthy No problems at this moment. If you did receive an alert message, your cron job's running time is longer then your cron job monitor's delay. alert There is an active issue with your cron job monitor. See your cron job monitor details for more information.
{
"status": "ok",
"reason": ""
}

get
Start

https://api.cronly.app/1.1/cron/start
To get more insights in your cron job's performance, you can use the start endpoint. We will store the time it takes between calling the start endpoint and the final pulse. This call should be called as early as possible. We advice you to set a short time-out for the call and handle exceptions carefully.
Request
Response
Request
Path Parameters
token
required
string
Your cron job monitor token
Response
200: OK
{
"status": "ok",
"reason": ""
}

get
Alert

https://api.cronly.app/1.1/cron/alert
You can manually send an alert request for your cron job.
Request
Response
Request
Query Parameters
token
required
string
Your cron job monitor token
message
optional
string
Customize the default error message.
Response
200: OK
{
"status": "ok",
"reason": ""
}

get
List

https://api.cronly.app/1.1/cron
Get a list of cron job monitors.
Request
Response
Request
Query Parameters
key
required
string
API key
offset
optional
integer
Start position for pagination, defaults to 0
limit
optional
integer
Max. amount of results for this result set, defaults to 25, max. 100
Response
200: OK
{
"status": "ok",
"reason": "",
"total": 5, // Number of results
"results": [ // All results
{
"id": 123,
"added": "2018-01-01 00:00:00",
"project": "Default",
"name": "Lorem ipsum",
"schedule": "* * * * *",
"previousRun": "2018-01-01 01:04:00",
"nextRun": "2018-01-01 01:05:00",
"lastCheck": "2018-01-01 01:04:25",
"lastPulse": "2018-01-01 01:04:15",
"timezone": "Europe/Amsterdam",
"status": "healthy",
"archive": 0, // Notice: If the value is 1, the cron job monitor is archived and inactive
"events": [ // Notice: Maximum is set to the last 10 events
{
"added": "2018-01-01 01:04:00",
"type": "alert",
"message": "Log message"
}
]
}
]
}