Monitoring

    API Endpoint Monitoring

    Monitor your API endpoints for uptime, response time, and expected responses.

    Part of API endpoint monitoring — the full answer, the facts and the alternatives in one place.

    Updated 2026-03-20
    2 min read
    api
    endpoint
    REST

    API Endpoint Monitoring#

    Go beyond homepage uptime checks. LemWatch lets you monitor individual API endpoints — REST, GraphQL, or webhook URLs — with precise assertions.

    Setting Up an API Monitor#

  1. Navigate to Site Details → API Endpoints tab
  2. Click "Add Endpoint"
  3. Configure:
  4. URL — The full endpoint URL (e.g., https://api.example.com/v2/health)
  5. Method — GET, POST, PUT, DELETE, HEAD, PATCH
  6. Expected status code — e.g., 200, 201, 204
  7. Expected body contains — Optional string that must appear in the response
  8. Custom headers — Add Authorization, API keys, or custom headers
  9. Timeout — Max wait time before marking as failed (default: 10s)

    10. What Gets Monitored#

    MetricDescription
    Status codeWhether the response matches your expected code
    Response timeMilliseconds to first byte
    Body assertionWhether expected content appears in the response
    Consecutive failuresHow many checks in a row have failed
    Average response timeRolling average across all checks

    Degraded vs Down#

    LemWatch distinguishes between degraded and down:

  10. Degraded — Endpoint responds but is slower than usual or returns unexpected content
  11. Down — Endpoint fails to respond, times out, or returns a server error

    12. Auto-Suggested Endpoints#

    When you add a site, LemWatch scans for common API patterns and suggests endpoints:

  12. /api/health, /api/status
  13. /wp-json/wp/v2 for WordPress
  14. /.well-known/ endpoints
  15. Sitemap and robots.txt URLs

    16. Alerts#

    API endpoint failures trigger the same alert pipeline as uptime checks. Configure per-endpoint thresholds in Settings → Alerts.

    Best Practices#

  16. Monitor your critical user flows — login, checkout, search
  17. Set realistic timeouts — API endpoints behind auth may be slower
  18. Use body assertions to catch cases where a 200 response contains an error message
  19. Monitor staging and production separately to catch deployment regressions
    20. Was this article helpful?

    Previous

    SLA Dashboard

    Next

    Fleet Health Overview

    Related Articles

    How do I monitor a JSON API endpoint?

    Add any HTTP endpoint under API Monitoring and Lemwatch checks status code, response time, and optional JSON body assertions every minute.

    How does API endpoint degradation alerting work?

    Lemwatch compares each endpoint's current response time against a rolling 24-hour baseline and alerts when it degrades by 2× or more.

    Uptime Monitoring

    How LemWatch checks if your website is online and responding.

    Setting Up Alerts

    Configure 11 notification channels — email, push, chat, on-call, and automation tools.

    API Endpoints Reference

    Overview of available API endpoints and their usage.

    SLA Tracking

    Define SLA targets and track compliance across your sites.

    Back to Help Center