Healthchecks.io Management API

Name: Healthchecks.io Management API
Brand: Healthchecks.io Management API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey13 EndpointsREST

For Agents

Create, configure, pause, and resume Healthchecks.io checks, read ping history and status flips, and list integration channels through the v3 Management API.

Install Jentic One Beta

Connect the Healthchecks.io Management API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Healthchecks.io Management API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Healthchecks.io Management API.

List existing checks and create new ones via /api/v3/checks/

Update an individual check's schedule and grace period through POST /api/v3/checks/{uuid}

Pause and resume a check via /api/v3/checks/{uuid}/pause and /api/v3/checks/{uuid}/resume

GET STARTED

Start building with Healthchecks.io Management API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Healthchecks.io Management API for, with concrete tasks.

★ Cron Job Monitoring at Provisioning Time

Whenever a new cron job, scheduled function, or queue worker is deployed, your provisioning code creates a matching check by POSTing to /api/v3/checks/ with the expected schedule and grace period. The job's last step pings the check URL, and Healthchecks.io alerts on the configured notification channel if the ping is missed. This couples job deployment to monitoring so nothing ships unmonitored.

POST to /api/v3/checks/ with name, schedule, and grace and verify the response contains a ping_url for the new check

Maintenance-Window Pause and Resume

When you take a service down for planned maintenance, call /api/v3/checks/{uuid}/pause to suppress alerts for the affected checks, then /api/v3/checks/{uuid}/resume when the service comes back. This avoids paging the on-call team during an expected outage and keeps the audit trail of why checks went silent. Use the bulk-list endpoint to find the right uuids by tag.

POST /api/v3/checks/{uuid}/pause for each check tagged 'database', wait for maintenance, then POST /api/v3/checks/{uuid}/resume for the same set

Incident Postmortem Data Pull

After an incident, pull the last N pings and status flips for the affected check via /api/v3/checks/{uuid}/pings/ and /flips/ to reconstruct exactly when the check went down and came back. The flips endpoint gives a clean state-change log, while the pings endpoint shows the body of the last failure ping if your job posted error context. Together these feed the postmortem timeline.

GET /api/v3/checks/{uuid}/flips/ for the last 24 hours and GET /api/v3/checks/{uuid}/pings/{n}/body for any failure pings in that window

AI Agent Monitoring Setup via Jentic

An infrastructure agent searches Jentic for 'create a cron job monitor' and Jentic returns Healthchecks.io's POST /api/v3/checks/ operation. The agent fills in name, schedule, and tags from the deployment context and creates the check, all without holding the API key directly because Jentic vaults it. This makes it easy to bolt monitoring onto an agent-driven deployment workflow.

Use Jentic search 'create a cron job monitor' to load /api/v3/checks/ and execute with name 'nightly-backup' and schedule '0 2 * * *'

Key Endpoints

13 endpoints — healthchecks.

METHOD

PATH

DESCRIPTION

GET

/api/v3/checks/

List checks

POST

/api/v3/checks/

Create a check

POST

/api/v3/checks/{uuid}

Update a check

DELETE

/api/v3/checks/{uuid}

Delete a check

POST

/api/v3/checks/{uuid}/pause

Pause a check

POST

/api/v3/checks/{uuid}/resume

Resume a check

GET

/api/v3/checks/{uuid}/pings/

List recent pings for a check

GET

/api/v3/checks/{uuid}/flips/

List up/down flips for a check

GET

/api/v3/checks/

List checks

POST

/api/v3/checks/

Create a check

POST

/api/v3/checks/{uuid}

Update a check

DELETE

/api/v3/checks/{uuid}

Delete a check

POST

/api/v3/checks/{uuid}/pause

Pause a check

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Healthchecks.io API keys grant project-wide read or write access. Jentic stores the key in the vault (MAXsystem) and attaches the X-Api-Key header at execution time so agents only see scoped tool results.

Intent-based discovery

Agents search Jentic for intents like 'create a cron job monitor' or 'pause a healthchecks check' and Jentic returns the matching v3 operations under healthchecksio with their input schemas.

Time to first call

Direct Healthchecks.io integration: half a day to wire create, pause, and ping flows. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Healthchecks.io Management API through Jentic.

What authentication does the Healthchecks.io Management API use?

The API uses an X-Api-Key header (apiKey scheme) for every Management API call. Read-only and read-write keys are managed in the project settings; Jentic vaults the key and attaches it on each call.

Can I create a Healthchecks.io check from the API?

Yes. POST to /api/v3/checks/ with name, tags, schedule (or timeout and grace), and the response returns a ping_url. Hitting that ping_url from your job is what marks the check up.

What are the rate limits for the Healthchecks.io Management API?

Healthchecks.io rate-limits the Management API to 100 requests per minute per project, as noted in the apis.json description. Bursting above that returns HTTP 429; back off and retry with jitter.

How do I pause a check during a deploy through Jentic?

Search Jentic for 'pause a healthchecks.io check', load the /api/v3/checks/{uuid}/pause operation, and execute with the uuid. Resume the same check with the /resume operation when the deploy finishes.

Is the Healthchecks.io API free?

Yes — Healthchecks.io has a free Hobbyist plan that includes API access; paid plans add more checks, integrations, and longer ping retention but use the same endpoints.

Can I read the body of a failed ping?

Yes. /api/v3/checks/{uuid}/pings/ returns recent ping metadata, and /api/v3/checks/{uuid}/pings/{n}/body returns the request body sent with the nth ping. This is useful for surfacing the error message your job posted at the time of failure.

Healthchecks.io Management API

Connect the Healthchecks.io Management API to your agent

Capabilities

Start building with Healthchecks.io Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs