Documentation

Fettle is uptime monitoring for developers. It checks HTTP endpoints, TCP ports, DNS records, SSL certificates, ping targets and cron heartbeats from three regions (Europe, US East, Asia-Pacific), opens an incident when a check fails, notifies over email, Telegram, Slack, Discord or webhooks, and publishes a status page.

Everything the dashboard does to your monitors, incidents, heartbeats and status pages, the public API does too — on every plan, free included. It is the same API the dashboard itself calls.

1. Create an API key in the dashboard, under Settings → API Keys.
2. Send it as a bearer token: Authorization: Bearer fettle_…
3. That is all. A key belongs to one organization, so there is no organization header to set.

Keys carry either read or write scope, and write implies read. Full reference: API keys.

• QuickstartFrom no account to a monitor checking your site, in three API calls: create a key, list monitors, create one.Read
• API keysHow Fettle API keys work: read and write scopes, rotation, IP allow-lists, and the per-plan request limits.Read
• MCPConnect Fettle to Claude, Cursor or Windsurf over the Model Context Protocol — a hosted endpoint or the fettle-mcp npm package.Read

Every public endpoint, with request and response schemas, is published as an OpenAPI document at /public-api/docs. It lists only the routes an API key may call — the dashboard’s own internal endpoints are deliberately absent, and a key cannot reach them.