API monitoring
API monitoring that checks the answer.
Check availability, response time and response content in one place. Catch a failed request or a missing field before a customer reports a broken integration.
Start monitoring your API25 monitors free · 60-second checks · no credit card
{"status":"ok","database":"offline"}Response check failed
The request succeeded, but the expected text "database":"online" is missing.
An HTTP status alone would miss this failure. Add a keyword check for the answer you expect.
Define a healthy response.
Configure an HTTP monitor for availability or a keyword monitor for response assertions. Both support custom requests and authentication.
- Send the right request
- Choose your HTTP method, headers and request body. Check the endpoint your integration actually calls.
- Authenticate the check
- Use Basic authentication, a bearer token or a custom authentication header for protected endpoints.
- Accept the right status
- Set the HTTP status codes that count as success for this endpoint, such as 200 or 204.
- Inspect the response
- Match or exclude text, use a regular expression, or check that a JSON path exists. A missing field can fail a check even when the server returns 200.
- Set a response-time limit
- Choose the maximum response time for the request so an endpoint that becomes too slow can fail its check.
From failed request to a team that knows.
Send alerts to email, Slack, Discord, Microsoft Teams, Telegram or a webhook. Connect the monitor to a status page so customers can see the health of the service too.
Start with a read-only health endpoint or a dedicated test resource. Repeated checks should not create real orders or charge customers.
- 1.
Add the endpoint
Choose HTTP or keyword, enter the URL, then configure the request and success criteria.
- 2.
Choose the schedule
Start at 60 seconds on Free. Paid plans support 30-second checks and multiple monitoring locations.
- 3.
Route the alert
Choose a notification integration and verify it reaches the team responsible for the API.
Start with the endpoints that matter.
Free includes 25 monitors, one location and 30 days of result history. Paid plans add faster checks, more capacity and longer history.
Compare plans and limits →Need a setup walkthrough?
- How to monitor an API
- API monitoring explained
- API readiness lab: code and results
- 247Monitor REST API documentation
The REST API manages your monitors programmatically. It is separate from monitoring your own endpoints.
Your questions, answered.
Can I monitor APIs for free?
Yes. Free includes 25 monitors shared across supported check types, with 60-second checks from one location. HTTP and keyword checks, six non-SMS alert integrations and one public status page are included. No credit card required.
Can I monitor an authenticated endpoint?
Yes. Configure Basic authentication, a bearer token or a custom authentication header. You can also supply request headers and a request body. Use credentials and endpoints intended for automated checks.
What can I check in an API response?
Set accepted HTTP status codes and a maximum response time. A keyword monitor adds text inclusion or exclusion, a regular expression, or a JSON path existence check. JSON path checks verify that a field exists; they do not validate a complete JSON schema.
Is this the same as access to the 247Monitor REST API?
No. Endpoint monitoring checks your API and is available on Free. The 247Monitor REST API lets you manage monitors programmatically and is available on paid plans.
No credit card · 25 monitors free
Start monitoring in minutes.
The free plan includes 25 monitors, one server and a public status page. Add your first check and choose where alerts should be sent.