Monitoring that keeps in step with your deploys
You can use the GraphQL API to add a monitor when a site launches, pause checks during maintenance and pull results into your own tools, with keys you can make read-only or limit to specific sites.
You can see the API shape before you wire it in
Real GraphQL fields, site-management mutations, and custom REST tools endpoints, so you can see exactly what each API surface looks like.
GraphQL uptime query
Reads active uptime monitors with only the fields your workflow needs.
query {
findUptimeLink(limit: 10) {
items {
id
name
target
status
checkInterval
lastRecord {
accessibilityStatus
spendTime
}
}
}
}Create site mutation
Adds a monitored site with the product areas your workflow needs.
mutation {
createSite(
domain: "acme.io"
features: [
MONITOR_WHOIS
MONITOR_SSL
MONITOR_DNS
LINK_CRAWLER
]
notification: { all: true }
) {
id
domain
features
notification {
all
}
}
}Custom REST tools request
Sales-enabled access for domain and DNS intelligence endpoints.
GET /api/tools/v1/dns/lookup?domain=acme.io&type=A,MX,SPF
Authorization: Basic api_key:api_secret
X-Daily-Limit: 500
X-Daily-Remaining: 482Examples are based on the current GraphQL schema and REST Tools OpenAPI contract. Standard API access is authenticated GraphQL access; REST tool access is enabled through custom sales arrangements.
Monitoring set up by hand falls behind your releases
WebPixie exposes a GraphQL API with full queries and mutations, so you can manage your monitoring programmatically: 20+ queries and 15+ mutations across monitors, uptime data, and incidents.
REST access to WebPixie’s Tools infrastructure is separate from standard plan API access and is enabled only through custom sales arrangements. When enabled, it exposes diagnostic tools WebPixie runs inside the product, such as DNS and domain lookups, so you can call them from your own code.
Authentication uses API keys over HTTP Basic auth. Each key inherits the workspace role of the user who created it and can then be narrowed to specific resources, so an automation scoped to one site cannot reach the rest of the workspace.
For event-driven workflows on higher plans, webhooks deliver incident creation and closure, SSL check and expiration events, and domain expiration and suspension events to your own endpoints after WebPixie generates them, so you can wire WebPixie into the tools your team already runs.
Prefer to work through an AI assistant instead of code? The MCP server connects assistants such as Claude, ChatGPT, Codex, and VS Code to your WebPixie account.
Endpoints and authentication are covered in the API docs.
Monitoring management over GraphQL
20+ queries and 15+ mutations
You can create and update monitors, pull uptime history, and read incident state from your own code. The GraphQL API offers queries and mutations across monitoring management, so many dashboard workflows can be scripted.
Every key scoped to the resources it needs
Inherited role, then narrowed to specific resources
A broad credential shared across scripts is a risk. A WebPixie key authenticates over HTTP Basic auth, inherits the role of the user who created it, and can be made read-only or narrowed to specific resources, so a key for one integration reaches only the sites and monitors it needs and nothing else in the workspace.
Webhook-driven workflows
Incident, SSL, and domain events
On higher plans, webhooks deliver generated events to your own endpoints: incident creation and closure, SSL check failures, SSL expiration, domain expiration, and domain suspension. You can connect them to Slack, PagerDuty or your deployment automation, so monitoring fits the response flow you already use.
Monitoring built into your pipeline
Monitors created at deploy time, data synced out
Because GraphQL covers monitoring management workflows, you can register new environments during a deploy, pull uptime and incident data into internal dashboards, and remove monitors when a service is retired, all without opening the WebPixie UI.
Monitoring built into your workflow
Once you create a key and choose what it can reach, you can connect it to your deploy pipeline.
Everything you need to monitor a website. In one workspace.
A quick look at other WebPixie features.
Why teams choose the WebPixie API
Automated setup and teardown
You create and remove monitors from your pipeline, so monitoring tracks your infrastructure instead of drifting from it.
Keys limited to what each job needs: read-only, or narrowed to specific sites and monitors
Resource-scoped keys over Basic auth keep automation credentials limited to what each integration needs.
Event-driven, not polling
On higher plans, webhooks deliver incident, SSL check, and SSL expiration events to your tools after WebPixie generates them, so you do not poll the API on a timer.
Frequently Asked Questions
Common questions about the WebPixie API.
Yes, WebPixie has a GraphQL API with more than 20 queries and 15 mutations, included on Starter, Pro, Enterprise plans. The API integration covers sites, uptime monitors, incidents, tags and workspaces, so a deploy script can create a monitor for a new environment, pause it during a release, resume it afterwards and read the latest analysis findings. Authentication uses API keys over Basic auth. A key acts with the workspace role of the user who created it, can be read-only and can be narrowed to specific sites and uptime monitors, so you never have to share a broad workspace credential. Teams also pull uptime history into internal dashboards and sync incident data with their own tools, and for alert-driven workflows the API pairs well with incident management and webhook notifications. The API docs cover endpoints and authentication setup. If you would rather work through an AI assistant than code, the MCP server connects Claude, ChatGPT, Codex and VS Code to your account on every plan.
Yes, but REST API access is separate from standard plan API access and is enabled through custom sales arrangements. 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 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 API surfaces use 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. GraphQL API access is available on Starter, Pro, Enterprise plans; REST tools API access is handled through sales-led arrangements.
Yes, your pipeline can call the GraphQL API to create, update, pause and resume monitors and to read monitor state, incidents and analysis findings after a deploy. A common setup pauses the production monitor before the release, resumes it afterwards and sets the expected keyword to the new build ID, so the next scheduled check confirms the right version is live. The API integration is available on Starter, Pro, Enterprise plans and uses API keys over Basic auth. A key can be read-only and limited to specific sites and monitors, so a CI job only touches the environment it deploys. Monitor creation is also capped per day at your plan's monitor limit, so it works best to keep one monitor per environment and update its target instead of creating a new one for every preview deploy. Checks run on each monitor's own interval. To get alerts into your own tooling, webhooks send incident events to an HTTPS endpoint you set, and each event matches a record in incident management. Webhook availability depends on plan, and you can compare plans on the pricing page.
Yes, WebPixie can post monitoring events to any HTTPS endpoint you set with webhooks, so your own service, an on-call tool or an internal bot can react to them. Events cover incident openings and closures for uptime and SSL checks, SSL and domain expiry warnings and domain suspensions. If your on-call tool expects its own format, a small relay service in between can translate the event. Email alerts work on every plan, Slack is a built-in channel on eligible plans and webhooks are part of the higher plans, so you can compare notification channels on the pricing page. Notifications are set per resource, so you can keep staging quiet while production alerts go out. Each event matches a record in incident management, where you can follow its duration and add notes, and the API integration lets your service query or update the same resources after it receives an event.
Yes, through webhooks: WebPixie posts incident and SSL/domain events to PagerDuty, and webhooks are available on higher plans. Webhooks send monitoring events to an HTTPS endpoint you configure, so PagerDuty can receive alert-routing events from WebPixie and route them through the policy your team already uses. This works best when paired with incident management, because confirmed failures become tracked incidents before they are routed externally. Webhook availability depends on plan, and you can compare notification channels on the pricing page. Programmatic workflows around the same resources are covered by the API integration.
Ready to automate your monitoring?
A GraphQL API, scoped keys, and event webhooks on higher plans.