Oh Dear

Get who this connection is authenticated as and which team it operates on, including the team timezone, how many monitors it has and whether its plan is active. Useful for grounding answers about "my" monitors and for telling which team a question applies to. See https://ohdear.app/docs/api/user-info.

Get the results of the AI check on a monitor: what the AI was asked to verify about the page, what it concluded, and why. Use this to see why an AI monitor passed or failed. See https://ohdear.app/docs/api/ai-powered-monitoring.

Get the application health checks a monitored site reports back to Oh Dear, such as queue depth, disk space, database connectivity or Horizon status, with each one's current status and message. This is the check that surfaces problems inside the application rather than on the network. See https://ohdear.app/docs/api/application-health.

List the broken links (dead URLs returning a 4xx or 5xx status) found on a monitored site during its most recent completed crawl, including the page each one was found on. See https://ohdear.app/docs/api/broken-links-crawled-urls.

Get the SSL/TLS certificate Oh Dear last saw for a monitor: issuer, validity dates, expiry date and the domains it covers. Use this to answer whether a certificate is valid or about to expire. See https://ohdear.app/docs/api/certificate-health.

Get the current result and a one-line summary for every check running on a monitor, or for one check type. This is the fastest way to answer "is anything wrong with this site right now" before drilling into a specific report. See https://ohdear.app/docs/api/check-summary.

Get what Oh Dear's crawler found on a site during its most recent crawl, falling back to a crawl still in progress if none has completed yet: either the mixed content (insecure http assets loaded on an https page, which make browsers show a warning) or a breakdown of every URL it visited, split into internal and external and counted by type. For the broken links themselves, use get_broken_links. See https://ohdear.app/docs/api/mixed-content.

List the cron job checks (heartbeat monitoring for scheduled tasks) configured on a monitor, with their schedule, current status and recent ping history, so you can see which scheduled jobs failed to report in. See https://ohdear.app/docs/api/cron-job-monitoring.

Get the DNS records Oh Dear last saw for a monitor, plus the history of changes to them, so you can spot when a record changed. This can return a lot of data, so start with limit 3 or 4. See https://ohdear.app/docs/api/dns-records.

Get what the outside world can see about a monitored domain: its registration and expiry details from whois/RDAP, the ports found open on it by the latest port scan, and whether its IPs appear on any DNS blocklist. Returns all three sections by default. See https://ohdear.app/docs/api/domain-monitoring, https://ohdear.app/docs/api/port-scanning and https://ohdear.app/docs/api/dns-blocklist.

List the outages Oh Dear recorded for a monitor, with the start and end of each one. Times are UTC. Returns the most recent outages up to the limit you set, and totals the downtime across just those, so widen the limit before drawing conclusions about a long period. See https://ohdear.app/docs/api/uptime.

Get the most recent Google Lighthouse reports for a monitor: performance, accessibility, best practices and SEO scores, Core Web Vitals metrics, and the issues that were flagged. See https://ohdear.app/docs/api/lighthouse.

List the one-off maintenance windows on a monitor, the ones with a fixed start and end. Alerts are suppressed while a window is active. For windows that repeat on a schedule, use get_recurring_maintenance_periods instead. Times are in the team timezone. See https://ohdear.app/docs/api/maintenance-windows.

List the recurring maintenance windows defined on a monitor, with their schedule and the maintenance periods recently generated from them. Alerts are suppressed while a maintenance window is active. See https://ohdear.app/docs/api/maintenance-windows.

Get the sitemap check results for a monitor: the sitemap indexes and sitemaps that were found, how many URLs each one contains, and any problems detected in them. See https://ohdear.app/docs/api/sitemap.

Get uptime and downtime percentages for a monitor over a date range, grouped per minute, hour, day, week or month, alongside the average response timings measured in each interval. Use this to answer how much downtime a site had. See https://ohdear.app/docs/api/uptime.

Search and list the team's monitors (the websites, hosts and services Oh Dear watches, also called sites) with their current up/down status, open issues and performance metrics. Pass monitor_id to fetch the full detail for one monitor. Start here when you need a monitor ID for another tool. See https://ohdear.app/docs/api/monitors.

List where Oh Dear sends alerts for a given scope: "team" (team-wide alerts), "tag" (alerts for monitors carrying a tag), or "monitor" (a single monitor's alerts). For tag-group routing, use list_tag_groups instead. See https://ohdear.app/docs/api/notification-destinations.

List the team's public status pages with their title, slug, custom domain and display settings. Pass status_page_id to fetch a single one. Start here when you need a status page ID for another tool. See https://ohdear.app/docs/api/status-pages.

List the incident updates posted on a status page, most recent first. Use this to see what your visitors are currently being told, or to find the ID of an update you want to edit. See https://ohdear.app/docs/api/status-pages.

List the team's tag groups with their tags and notification destinations. A tag group routes alerts to destinations such as an email address for every monitor carrying one of the group's tags. See https://ohdear.app/docs/api/tags-and-tag-groups.

List the team's tags and which monitors carry each one. Tags drive notification routing through tag groups, so start here when you want to see how monitors are grouped. See https://ohdear.app/docs/api/tags-and-tag-groups.