Watchfox

Watchfox Docs

Help center for monitoring, alerts, status pages and reports.

Start with customer help docs for using Watchfox. Developer/API docs are separated in their own section with API reference, authentication, rate limits, CSV exports, OpenAPI, and Postman downloads. Security, privacy, legal, roadmap, changelog, and support contacts are linked here so docs act as a real trust surface, not an isolated file index.

Browse help docs Developers / API Contact support
Last updated: 2026-05-02 Public docs path: /docs/

Customer help docs

Product help first. These links stay inside the help hub and do not open JSON, YAML, or raw download files.

Start here

Getting started

Create a workspace, add a project, and get to the first useful monitor quickly.

 Open guide → Monitoring

Monitor types

Uptime, Keyword, TLS, Heartbeat, Sitemap, and Domain monitoring basics.

 Open guide → Alerting

Alerts

Alert channels, first alert delay, repeat reminders, recovery alerts, and maintenance mute.

 Open guide → Client-facing

Status pages

Publish service health, incidents, maintenance, and customer-safe operational updates.

 Open guide → Reporting

Reports

Monthly client reports, branded PDFs, report targets, trends, and export links.

 Open guide → Account

Billing

Plans, limits, upgrades, downgrades, cancellation, failed payments, and refunds.

 Open guide → Help

Troubleshooting

Timeouts, redirects, false positives, TLS/domain unknown states, and broken links.

 Open guide →
Getting started

Create your first useful monitoring setup

Use this flow when you are new to Watchfox or setting up a new client/project.

  • →Create workspace and project — separate client or site groups cleanly.
  • →Add first monitor — start with Uptime or Keyword for fast value.
  • →Add alert channel — email, Slack, webhook, Teams, Discord, or Google Chat.
  • →Create a status page or report — show value to clients and stakeholders.
Monitor types

Choose the right check for each site or workflow

Watchfox focuses on website and web-service monitoring.

  • →Uptime — HTTP/HTTPS availability, status code, and latency.
  • →Keyword — expected text present or missing on a page.
  • →TLS — certificate validity and expiry awareness.
  • →Heartbeat — missing cron or scheduled job pings.
  • →Sitemap — sitemap availability and broken links within sitemap scope.
  • →Domain — domain expiry risk via source-limited registry data.
Alerts

Control when and how notifications are sent

Use alert timing to reduce noise while still catching real incidents.

  • →First alert delay — wait before sending the first DOWN alert.
  • →Repeat reminders — keep teams informed while an issue persists.
  • →Recovery alerts — notify when the service is back UP.
  • →Maintenance mute — suppress expected downtime during planned work.
  • →Paused and archived behavior — paused monitors and archived projects should not create surprise alerts.
Status pages

Share public-safe service health

Status pages are designed for client-facing communication, not raw internal debugging.

  • →Components — map monitors to customer-readable service names.
  • →Incidents — show current and historical service issues.
  • →Maintenance — separate planned work from unexpected downtime.
  • →Subscriptions — let users receive public-safe updates where enabled.
Reports

Produce client-friendly monthly evidence

Reports summarize what happened without exposing internal secrets or raw debug data.

  • →Monthly PDF — client-facing summary with uptime, incidents, and trends.
  • →Report branding — customize monthly PDF brand name, logo, and footer note where your plan allows it.
  • →Targets — compare actual uptime with an optional reporting target.
  • →CSV exports — use authenticated exports for detailed data.
Billing

Understand plans, limits and billing support

Billing is plan-aware and enforced server-side, not only in the UI.

  • →Plans and limits — monitor count, status pages, probe coverage, reports, branding, and API.
  • →Upgrade or downgrade — plan changes can affect limits and feature availability.
  • →Cancel or refund — contact [email protected].
  • →Merchant of Record — Paddle handles payment processing, tax, and invoices.
Troubleshooting

Investigate common monitoring questions

Start here when a check looks wrong or unclear.

  • →False positives — check status code rules, redirects, timeouts, and maintenance windows.
  • →TLS warning or unknown — certificate data can be delayed or provider-limited.
  • →Domain unknown — registry/RDAP sources may be source-limited.
  • →Sitemap broken links — inspect sampled URLs and response codes.
  • →Heartbeat missing ping — verify the cron job calls the heartbeat URL on schedule.
  • →Keyword mismatch — verify exact text, redirects, rendered content, and case-sensitive expectations.

Developers / API

API documentation remains in English and is separated from the customer help navigation.

Reference

API reference

Use the Public API for project-scoped integrations, automations, monitor data, incidents, and export workflows.

  • →Open API reference — English Markdown reference for current API behavior.
  • →Authentication — covered in the API reference: project API key and signed-in Bearer session notes.
  • →Rate limits — covered in the API reference: headers, 429 behavior, and retry expectations.
  • →CSV exports — covered in the API reference: export format, cursors, and limits.
Downloads

Machine-readable API assets

These are explicit developer downloads, not customer help pages.

Trust, transparency and support

Legal, security, privacy, system status, roadmap, changelog, and support entry points are linked directly from the docs hub.

Security Responsible disclosure and security contact. Status Current Watchfox service status and incident history. Privacy Operational telemetry and data handling. Legal hub Terms, Privacy, Refunds, DPA, and security links. Terms Service terms for Watchfox customers. Refunds Cancellation and refund policy. DPA Data Processing Addendum. Changelog Customer-facing product changes. Roadmap Planned improvements grouped by confidence. Support [email protected]
Support entry point

Need help or want to report a security/privacy issue?

Start with support for product questions. Use the dedicated trust mailboxes for security reports, privacy requests, billing questions, or abuse reports.