Website Monitoring API for Developers

Yes, WebPixie provides a GraphQL API for teams that want to manage monitoring programmatically. The API integration includes queries and mutations for working with monitors, uptime data, incidents, workspaces, and related monitoring resources. Authentication uses resource-scoped API keys with Basic auth, so you can limit access by resource instead of sharing a broad workspace credential. API access is available on Pro, Enterprise plans, and you can compare plan availability on the pricing page. Developers can use the API to create monitors during deployments, pull uptime history into internal dashboards, sync incident data, or connect WebPixie with automation tools. For alert-driven workflows, API usage pairs well with incident management and webhook notifications.

Yes, alongside the GraphQL API there is a REST API, and the two serve different purposes. The GraphQL API in the API integration is how you manage monitoring programmatically, with queries and mutations for monitors, uptime data, incidents, and workspaces. The REST API is built on WebPixie's Tools infrastructure and exposes the diagnostic tools WebPixie runs inside the product, such as DNS lookup and domain or WHOIS lookup, as services you can call from your own code. It is not a second way to manage your account; monitoring management stays in GraphQL. Both authenticate with API keys over Basic auth, where a key inherits the workspace role of the user who created it and can then be narrowed to specific resources. API access is available on Pro, Enterprise plans, it pairs well with webhook notifications and incident management, and you can compare availability on the pricing page.

Yes, you can integrate WebPixie with CI/CD pipelines using the GraphQL API and webhook notifications. After a deployment, your pipeline can create or update monitors, register new environments, query uptime or incident state, and feed monitoring results into release checks or internal dashboards. The API integration uses API keys with Basic auth and resource-scoped access, which helps keep automation credentials limited to the resources they need. Webhooks can send incident creation, incident resolution, SSL expiration, and domain expiration events to tools such as Slack, PagerDuty, Opsgenie, or your own deployment automation. This works well when paired with incident management, because confirmed monitoring failures can trigger the same response flow your team already uses. API and webhook availability depends on plan, so compare access on the pricing page.

WebPixie supports custom webhooks that send monitoring events to any HTTPS endpoint you configure. Webhooks are useful for tools such as PagerDuty, Opsgenie, incident management platforms, CI/CD automation, internal dashboards, and custom notification systems. Supported event flows include incident creation and resolution for uptime checks, SSL check failures, SSL expiration, and domain expiration. The API integration works alongside webhooks, so teams can receive event-driven callbacks and then query or update resources programmatically. Slack is available as a native notification channel on eligible plans, while webhooks let you connect to systems beyond built-in integrations. Webhook availability depends on plan, so compare notification channels on the pricing page. For alert routing and incident lifecycle details, see incident management.

Yes, WebPixie can monitor staging, development, preview, and production environments when they are reachable by WebPixie checks. Public staging URLs can be monitored with standard uptime monitoring, including expected status codes, response time checks, body keyword validation, and custom request settings. Password-protected or token-protected environments can also be checked when you configure supported authentication details, such as Basic auth credentials or static custom headers. Teams often organize staging, development, and production monitors in separate workspaces or resource groups so permissions and alerts stay clear. Workspace management helps control who can create monitors, view reports, or change settings, and plan limits can be compared on the pricing page.