Send Pulse heartbeats from scripts

API and WebhooksUpdated Jul 16, 20263 min read

Issue a Pulse token for the monitor, then send a POST request to /v1/heartbeats/[heartbeat-token] after the work completes.

Keep the token secret and never place the real value in documentation, source control, or logs.

Send a JSON body with Content-Type: application/json containing status as success or failure and an RFC3339 observed_at timestamp.

An empty body cannot provide the required status and timestamp, so it is not accepted as a heartbeat.

The endpoint returns an accepted heartbeat ID when it records the event.

Use the monitor’s recent checks and history to confirm the recorded evidence.

Setting up a heartbeat for a cron job

Create a Pulse, keep its endpoint token private, and report only after successful work.

3 min read

Keep API keys in a secret store and rotate them by creating a replacement before revoking the old key.

2 min read