API overview

The Servor public API — base URL, versioning, scoped tokens, and what you can read and automate, from servers and monitors to incidents.

The Servor public API lets you read your infrastructure and drive incident automation programmatically. It's a lean, read-first surface: infrastructure changes (creating servers, monitors or status pages) stay in the dashboard, and command execution is never exposed to a token — commands are signed in your browser, which an API token cannot do.

Base URL

https://api.servor.app/v1

All endpoints are versioned under /v1 and return JSON. Timestamps are ISO 8601 in UTC.

What you can do

Read servers, monitors and their checks, status pages, incidents, command history and the audit log.
Automate incidents — create incidents, post updates and resolve them, which makes the API ideal for wiring your own alerting into Servor.

Getting started

Create a token in Settings → API tokens — see API tokens.
Send it as a Bearer header — see Authentication.
Grant only the scopes you need.

Mind the rate limits and handle errors — both are documented and stable.

Download the spec

Import the full token-authenticated surface into your tooling — OpenAPI 3.1 or a ready-to-use Postman collection. Both cover only the /v1 routes; set your sv_live_ token after importing.

Download OpenAPI Postman collection

The token-authenticated /v1 surface. Import the OpenAPI or the Postman collection, then set your sv_live_ token.

Reference

Browse endpoints by resource:

Servers APIList servers and read one server's details.Monitors APIRead monitors and their check history.Incidents APICreate, update and resolve incidents.Status pages APIRead pages, components and public incidents.Command history APIRead a server's recorded commands.Audit log APIRead your team's activity record.