The Cronitor API Basics

Cronitor is built for developers, and every feature on our dashboard is powered by API endpoints that you can use yourself

͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏
  ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏
  ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏
  ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏
  ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏
  ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏
  ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­͏   ­

Emre,
Cronitor is built for developers, and every feature on our dashboard is powered by API endpoints that you can use yourself to
integrate Cronitor with your own workflows and applications.
Using our REST API
Our Rest API [https://cronitor.io/docs/api] is organized around capabilities and we expose resources like monitors, issues and
metrics. API keys created with read/write permission can fully manage these resources using our API, from provisioning to cleanup.
All endpoints are JSON-based, and an HTML view is available for logged-in users when you visit any endpoint in a web browser.
Batch Upsert Endpoints
In addition to the normal create and update semantics, some batch resources including monitors support idempotent PUT requests
that use update-or-create "upsert" to efficiently manage a large number of monitors in a single request. We use these endpoints
with our own auto-provisioning features in CronitorCLI, Cronitor for Kubernetes, and other SDKs.
Manage your Monitoring with YAML
Declaratively manage your Cronitor resources with local YAML files
[https://github.com/cronitorio/cronitor-python?tab=readme-ov-file#configuring-monitors] that can be kept in version-control and
synced to Cronitor using any of our popular SDKs. Integrate Cronitor provisioning into your own build process and maintain a
single source of truth for your infrastructure monitoring directly beside the code itself.
Automatic Provisioning with the Telemetry API
Designed specifically for event processing, the Telemetry API works differently than our REST API. One major difference is that
GET, POST, and HEAD requests are all processed in the same way by turning the request into an incoming event in our ingestion
pipeline. Monitor details can't be retrieved from the API, but it does include its own ability to create monitors on the fly when
telemetry is sent to a new monitor key that doesn't yet exist.


Getting Started with the Cronitor API

When you signed up we created two API keys automatically, a read/write REST API key, and a telemetry-only key. Copy your
read/write key from the settings pane [https://cronitor.io/app/settings/api]l and head over to our API Docs
[https://cronitor.io/docs/api] to get started. If you prefer not to use the REST API directly, we offer SDKs for a number of
popular languages.

https://github.com/cronitorio

See our docs for a complete list of our SDKs [https://cronitor.io/docs/sdks], or check them our directly on our Github
[https://github.com/cronitorio]. We have official SDKs for Python, PHP, JavaScript and many more.

Install an SDK [https://cronitor.io/docs/sdks]



Cronitor Dashboard [https://cronitor.io/app] | Welcome to Cronitor [https://cronitor.io/app/welcome]
 
You are receiving this email because you opted in to receive updates from Cronitor
Cronitor, 1214 Parker Street, Berkeley, CA 94702
Unsubscribe [https://app.loops.so/unsubscribe/cmw1a8f663diq01tw8vd39hlp/3908a67d7806a847f59928bc3c6f0d4d4ed3eb326b177710a8fae0a69650443c96f217d2ac5195c641c98bf375c84b60d30b5ab7b51801e563fb2cac]

Accession

nse/cronitor/2026-11-03/6077

From

Cronitor · support@cronitor.io

Sent

3 November 2026 · 22:00 UTC