/api/v1. Responses use stable resource shapes designed for integrations and automation.
What you can do with the API
Teams
List teams, plan limits, and monitoring defaults
Sites
Create and manage monitored sites
Checks
Create on-demand checks and read results
Reports
Pull uptime and performance reports
Issues
Read monitoring incidents and lifecycle history
Base URL
All API endpoints use this base URL:All paths in this documentation are relative to the base URL unless noted otherwise.
Quick start
1
Create an API token
In the Sitepulse dashboard, open Settings → API tokens. Create a personal access token and select the scopes your integration needs (for example
sites:read, sites:write, checks:run).2
Call the API
Use the token in the
Authorization header:3
Work inside a team
Most write operations require an active team context. Team-scoped routes resolve the team from the URL (
/teams/{team}/sites) or from the site or check in the path.4
Create a site and run a check
Only
url is required. New sites inherit the team’s monitoring defaults; to enable specific tools or set cadences at creation, send a monitoring_settings object.Versioning
Only/api/v1 is documented here. Breaking changes will ship under a new version prefix.
Requirements
Before using the API, ensure you have:- A verified Sitepulse user account (email verified)
- An active subscription on the team you are accessing (inactive billing returns
402) - API token scopes that cover the operation (missing scope returns
403) - Team membership and role permissions for the underlying action (returns
403or404as appropriate)
API documentation
Authentication
Personal access tokens, OAuth scopes, and required headers
Requests & Responses
JSON conventions, pagination, team context, errors, and rate limits
Resources
Field-by-field schemas for users, teams, sites, checks, issues, and reports
Endpoints
Complete HTTP method and path reference
Check Results
Result object shapes per check tool