Customer API for integrations (Zapier, Make, custom scripts). Authenticate with a Bearer token; use team_id as a query or body parameter for team-scoped endpoints.
Authentication: Send your API token in the Authorization header as Bearer {token}. Create tokens from Account → API tokens (team owners only). You cannot use the API without a valid token.
Team-scoped endpoints: Endpoints that list or modify team resources (websites, checks, alerts, team users) require team_id. Send it as a query parameter (e.g. ?team_id=2001) or in the request body for POST/PATCH. You must be a member of that team.
Request format: All requests and responses are JSON. Send Content-Type: application/json and Accept: application/json.
API requests are rate limited. If you exceed the limit you will receive 429 Too Many Requests. Respect the Retry-After header when present.
Non-2xx responses use a consistent JSON shape: message (string) and optionally errors (object for validation). Common codes: 401 Unauthenticated, 403 Forbidden, 404 Not found, 422 Validation failed, 429 Rate limited.
- Create a token in Account → API tokens. 2. Call
GET /api/me with Authorization: Bearer YOUR_TOKEN. 3. Call GET /api/team?team_id=YOUR_TEAM_ID. 4. Call GET /api/websites?team_id=YOUR_TEAM_ID.