Cronitor provides fast and reliable uptime and correctness monitoring for JSON APIs. Our global healthchecks provide you with:
In this guide we'll create a new API monitor from the Cronitor dashboard, and we'll examine the various types of assertions that can be configured to validate your API responses.
Tip: If you are planning to create API monitors using our Monitor API, we recommend first following the directions below. Once you've created your first API monitor, click the "Monitor Detail" link on that monitor to view a JSON representation. Use this as a reference while creating your integration.
POST, etc. You can also adjust the frequency and regions of the healtchecks.
Nota Bene: APIs like Stripe, Plaid and Cronitor use `Basic` authentication over HTTPS. If your API uses this same authentication mechanism, first locate your API key and append a
: to it. Then use a base64 encoder to generate the encoded value. Insert that value as
Combine multiple service health assertions with our built-in checks for total and intermittent downtime to create the right healthcheck solutions for your services. Available assertions include:
Configurable operators for these rules include
Healthchecks can be configured to ping your endpoint as often as once every 30 seconds, however each plan has a maximum number of allowed healthcheck requests each calendar month. If this quota cannot accommodate your use case, please reach out to email@example.com for assistance.
Cronitor for Business:
3,000,000 Healthcheck requests per month
Cronitor for Teams:
1,000,000 Healthcheck requests per month
250,000 Healthcheck requests per month
All health check requests will be made with the User Agent
Monibot from our monitors in California, Oregon, Ohio, Virginia, Ireland and Tokyo. Outages are verified across multiple regions to determine failure scope.