API, monitoring as code & team administration — found from sitemap — Cronitor

Cited by

Facts read from this source

• Monitor API purpose Report an error

  “The Monitor API allows you to configure monitor settings, including schedules, assertions, alert preferences and more.”

• Monitor types Report an error

  “The two required attributes are type ("job"|"check"|"heartbeat"|"site") and key, the unique identifier for the monitor.”

• Monitor create update Report an error

  “Monitors are created or updated by making a PUT request to the /monitors endpoint.”

• Monitor create single Report an error

  “Monitors can also be created individually by making a POST request.”

• Ssl certificate assertion Report an error

  “"ssl_certificate.expires_in > 30 days",”

• Custom metrics aggregates Report an error

  “Aggregates: sum, mean, min, max, p50, p90, p95, p99”

• API read monitors Report an error

  “Monitors can be retrieved in bulk by making a GET request to the top level monitors resource.”

• API filtering Report an error

  “The monitors endpoint supports several query parameters for filtering and searching:”

• API search Report an error

  “# Use the dedicated search endpoint for advanced search curl -X GET "https://cronitor.io/api/search?query=backup" -u API_KEY:”

• API pagination Report an error

  “# Paginate results curl -X GET "https://cronitor.io/api/monitors?page=2&pageSize=25" -u API_KEY:”

• Monitor delete Report an error

  “Monitors can be deleted individually by making a DELETE request that includes a monitor key in the URL.”

• Monitor bulk delete Report an error

  “Multiple monitors can be deleted in a single request by making a DELETE request to the monitors endpoint with a JSON body containing an array of monitor keys.”

• Bulk delete audit Report an error

  “Audit logs are created for each deleted monitor”

• Monitor clone Report an error

  “You can create a copy of an existing monitor by making a POST request to the /monitors/clone endpoint.”

• Monitor pause Report an error

  “You can programmatically pause and resume monitor evaluation using the pause endpoint.”

• Pause group bulk Report an error

  “# Pause all monitors in the "production" group for 4 hours curl -X GET "https://cronitor.io/api/groups/production/pause/4" -u API_KEY:”

• Pause behavior jobs Report an error

  “Cronitor continues to receive and record telemetry events No alerts are dispatched for schedule or assertion violations”

• Pause behavior checks Report an error

  “Cronitor stops making outbound requests to the monitored endpoint”

• Create paused Report an error

  “You can also create monitors in a paused state:”

• Assertion evaluation frequency Report an error

  “Monitors are evaluated multiple times per minute for both schedule and assertion violations.”

• Consecutive alert threshold Report an error

  “The maximum number of consecutive alerts to send without recovery before automatically pausing further alerts. Alerting resumes when the monitor recovers. Applies to free accounts, excluding check monitors.”

• Failure tolerance Report an error

  “job & heartbeat: number of telemetry events with state='fail' to tolerate before sending an alert.”

• Grace seconds Report an error

  “grace_seconds[integer default:60 type=job, 0 otherwise]”

• Notify default list Report an error

  “All accounts have a default Notification List (key="default"). If notify is left empty or omitted, the default list will be used.”

• Job platforms Report an error

  “linux cron (default), windows, kubernetes, jvm, laravel, magento, sidekiq, celery, jenkins, quartz, spring, cloudwatch, node-cron,”

• Check platforms Report an error

  “http (default), browser(executes javascript), tcp, udp”

• Realert interval Report an error

  “Interval expression telling Cronitor how long to wait before sending follow up alerts after a monitor fails (and does not recover).”

• Request timeout Report an error

  “timeout_seconds integer 1 to 15 default: 10 - The timeout enforced when making the request.”

• Request limits Report an error

  “headers hash - The HTTP headers of the request (e.g. User-Agent). Limited to 5120 chars.”

• Check schedule range Report an error

  “An interval expression must be used. The range of accepted values is 30 seconds to 24 hours.”

• Schedules multiple Report an error

  “As of API version 2025-11-28, the schedule field has been replaced by schedules, an array of schedule expressions. This allows monitors to have multiple schedule expressions (e.g., for Windows Task Scheduler RRULE triggers or multiple cron expressions).”

• Schedule tolerance Report an error

  “Number of missed scheduled executions to allow before sending an alert.”

• Environments Report an error

  “Environments allow you to track monitor status separately across different deployment environments.”

• Statuspages integration Report an error

  “When a monitor fails, it can automatically create an incident on the associated status pages if the status page component has autopublish enabled.”

• Status badges Report an error

  “Available in API version 2025-11-28 and later. Replaces the public_badge_url and public_detailed_badge_url fields.”

• Telemetry endpoint Report an error

  “https://cronitor.link/ping/API_KEY/:monitorKey”

• Yaml import export Report an error

  “Cronitor supports importing and exporting monitor configurations in YAML format, which is useful for version control, bulk operations, and infrastructure-as-code workflows.”

• Yaml async Report an error

  “For large monitor configurations that may take time to process, Cronitor supports asynchronous YAML uploads.”

• Webhook requirements Report an error

  “HTTPS Only: Webhook URLs must use HTTPS for security Timeout: Webhooks will timeout after 30 seconds Retries: Failed webhook calls are retried up to 5 times with exponential backoff”

• Rate limiting Report an error

  “429 Rate Limited Reduce request frequency”

• API scopes Report an error

  “Check that your API key has monitor:read and monitor:write scopes”

• Latest invocations Report an error

  “An array of recent job invocations showing run/complete pairs. Available when requesting monitor details with withInvocations=true.”

• Readonly initialized Report an error

  “Whether the monitor has received its first telemetry event. A monitor is considered initialized after Cronitor receives at least one ping.”

• Custom metric names Report an error

  “Custom metric names seen on this monitor in the current environment over the last 7 days, most recent first, capped at 100.”

• Sdk available Report an error

  “Cronitor's open-source SDKs are the easiest way to use this API.”

2 facts read from this page are not shown because they could not be confirmed on the page as captured.

Scores citing this record

• The Agency Developer Checks, locations & failure confirmation
• The Agency Developer Alerting, escalation & on-call
• The Agency Developer API, monitoring as code & team administration
• The Customer Support Lead Checks, locations & failure confirmation
• The Customer Support Lead API, monitoring as code & team administration
• The Customer Support Lead Uptime reports, data & the vendor's own reliability
• The E-Commerce Operations Manager Checks, locations & failure confirmation
• The E-Commerce Operations Manager API, monitoring as code & team administration
• The SaaS Platform Engineer Checks, locations & failure confirmation
• The SaaS Platform Engineer API, monitoring as code & team administration
• The SaaS Platform Engineer Uptime reports, data & the vendor's own reliability
• The Information Security Officer Checks, locations & failure confirmation
• The Information Security Officer Alerting, escalation & on-call
• The Information Security Officer API, monitoring as code & team administration
• The Information Security Officer Uptime reports, data & the vendor's own reliability
• The Skeptic Checks, locations & failure confirmation
• The Skeptic Alerting, escalation & on-call
• The Skeptic API, monitoring as code & team administration
• The Skeptic Uptime reports, data & the vendor's own reliability