REST API and public status JSON
Quick answer
StillOnline exposes a public read-only status JSON at /v1/public/status/{slug} (no API key) and a private REST API v1 for projects, checks, and incidents on Pro ($9/mo) and Ultimate ($29/mo). OpenAPI spec at /openapi.json. Free has no API access. Pair with MCP for AI agent workflows.
Benefits
- Machine-readable status — scripts and agents poll JSON instead of HTML.
- Automation — create checks after infra changes (paid).
- Incident API — post updates from CI or runbooks (Pro+).
- Stable contract — documented in API docs.
- Public + private split — customers see public JSON; you use keys for management.
How it works
Public (no key):
curl -s https://api.stillonline.tech/v1/public/status/your-slug
Returns project name, operational status, active incidents, last updated.
Private (API key):
- Upgrade to Pro or Ultimate.
- Create a key in settings.
- Call
https://api.stillonline.tech/v1/...withAuthorization: Bearer .... - See docs/api for projects, checks, incidents.
Plan availability
| Plan | Public status JSON | Private v1 API |
|---|---|---|
| Free | Yes (for your public page) | No |
| Pro | Yes | Yes |
| Ultimate | Yes | Yes |
FAQ
Is the public status JSON free to use?
Yes for public status pages. Rate limits apply; do not use it as a high-frequency load test against our API.
Does StillOnline have webhooks for check events?
Outbound webhooks for check state are not shipped in v1. Use polling, Slack/Telegram owner alerts, or MCP.
Where is the OpenAPI spec?
https://stillonline.tech/openapi.json and docs/api.
Can I manage checks from GitHub Actions?
Yes on Pro+ with an API key—typical pattern after deploy. See blog guides on REST automation.