Founding customer pricing
Exploring DataPlug for your team?
Tell us what you need to monitor, and let’s discuss an early-customer plan.
200 OK. Empty results. Not quite okay.See an example →
API monitoring for small engineering teams
Monitor APIs you provide or depend on. Catch failed checks, invalid responses, and slow replies.
Example check
Catalog API
https://api.example.com/catalog
Expected: HTTP 200 · API key authentication
Validation: results array must not be empty
Response-time limit: 3 seconds
Check failed · HTTP 200 · 412 ms
Results array is empty.
The endpoint responded successfully, but its response failed the configured validation rule.
Check access, response content, and response time—using rules you define for the endpoints that matter to your service.
Send a bearer token or API key with each check, including a custom header name for API keys. Monitor endpoints that require credentials, not just public URLs.
Bearer token · API key header
Check that a required field exists or an expected array is not empty. Flag responses that fail your rules—even when the endpoint returns 200 OK.
Field exists · Array is not empty
Set a maximum response time from 1 to 15 seconds. Mark a check as failed when the endpoint responds but exceeds your limit.
Configurable response-time limit: 1–15 seconds
Check that the endpoints your customers depend on meet your response rules—not just return a successful status.
Check critical third-party endpoints against your requirements, with failed-check results to help investigate when something changes.
Enter the URL, the HTTP method, and the status code you expect.
Optionally add a bearer token or API key, one JSON rule, and a maximum response time.
Checks run every 5 minutes. When a monitor goes down or recovers, DataPlug posts to your webhook.
Exploring DataPlug for your team?
Tell us what you need to monitor, and let’s discuss an early-customer plan.
Start monitoring for free, with checks every five minutes.