Pinging API

With the Pinging API, you can signal success, fail, and start events from your systems.

General Notes

All ping endpoints support:

Successful responses will have the "200 OK" HTTP response status code and a short "OK" string in the response body.

Send a "success" Signal

HEAD|GET|POST PING_ENDPOINT{uuid}

Signals to SITE_NAME that the job has completed successfully (or, continuously running processes are still running and healthy). The uuid parameter is unique for each check.

Example

GET /5bf66975-d4c7-4bf5-bcc8-b8d8a82ea278 HTTP/1.0
Host: hc-ping.com
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 29 Jan 2020 09:58:23 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 2
Connection: close
Access-Control-Allow-Origin: *

OK

Send a "fail" Signal

HEAD|GET|POST PING_ENDPOINT{uuid}/fail

Signals to SITE_NAME that the job has failed. Actively signaling a failure minimizes the delay from your monitored service failing to you receiving an alert.

Example

GET /5bf66975-d4c7-4bf5-bcc8-b8d8a82ea278/fail HTTP/1.0
Host: hc-ping.com
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 29 Jan 2020 09:58:23 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 2
Connection: close
Access-Control-Allow-Origin: *

OK

Send a "start" Signal

HEAD|GET|POST PING_ENDPOINT{uuid}/start

Sends a "job has started!" message to SITE_NAME. This is optional but enables a few extra features:

Example

GET /5bf66975-d4c7-4bf5-bcc8-b8d8a82ea278/start HTTP/1.0
Host: hc-ping.com
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 29 Jan 2020 09:58:23 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 2
Connection: close
Access-Control-Allow-Origin: *

OK