- Home
- Api Docs
Website monitoring API
Lemwatch gives you one REST endpoint for uptime, response time, SSL and incident data on any site you monitor, and a POST call that runs a fresh check on demand. Authenticate with a bearer API key, get JSON back, 100 requests an hour by default. Keys are created in Settings → API Keys once you have an account.
Using an AI assistant? Try the MCP server instead
Connect Claude, ChatGPT, or Cursor directly to Lemwatch — 19 tools, 5 live resources, 6 playbooks.
Authentication
All API requests require an API key
Generate an API key from Settings → API Keys in your dashboard. Include it in the Authorization header:
Authorization: Bearer YOUR_API_KEYBase URL
Rate Limits
Default: 100 requests/hour per API key. Custom limits can be configured per key. Exceeding the limit returns 429 Too Many Requests.
Endpoints
GET/public-api
Get site status and metrics
site_idincludePOST/public-api
Trigger a site check
actionsite_idError Codes
Common questions
Does Lemwatch have an uptime monitoring API?
Yes. A single GET endpoint returns current status, 24-hour, 7-day and 30-day uptime, response time and health score for any site on your account, and a POST call runs a fresh check immediately. Responses are JSON.
How do I get an API key?
Create an account, add a site, then open Settings → API Keys and generate one. Keys are shown once and stored hashed. Send it as Authorization: Bearer YOUR_API_KEY. API access is a paid-plan feature; alert webhooks and the MCP server work on the free plan.
Can I connect it to Slack, Zapier, n8n or a webhook?
Yes. Alerts can post to Slack, Discord, Telegram, Microsoft Teams, PagerDuty and any webhook URL without writing code, and the API can be polled from Zapier, Make or n8n on a schedule. See the alert integrations pages for each channel's setup steps.
Can an AI assistant read my monitoring data?
Yes — the Lemwatch MCP server connects Claude, ChatGPT and Cursor straight to your sites, incidents, SSL and SEO data without you writing any API code.

