Monitor management · Monitor types
Use an API monitor
Monitor API endpoints and health routes with the correct method, status code, headers, and authentication. The guide follows the same monitor workflow used in the dashboard, so you can create, pause, remove, and troubleshoot monitors with confidence.
When to use it
Use an API monitor for health endpoints, API routes, backend services, or internal workflows exposed over HTTP or HTTPS.
Recommended settings
- Choose the HTTP method that matches the endpoint.
- Set the expected status code, such as 200 for a healthy health check or another intentional success code.
- Add headers for API keys, bearer tokens, content type, tenant routing, or versioning.
- Use basic authentication only when the endpoint uses HTTP basic auth.
- Use a lightweight health endpoint when possible so monitoring does not create unnecessary application load.
Avoid side effects
Monitoring should not create records, charge customers, mutate data, or trigger business workflows unless the endpoint is specifically designed for safe health checking.
Prefer health endpoints
A dedicated read-only health endpoint is usually better than monitoring a full business action.