Create a restricted token
Choose only the scopes and monitors your application needs. The token is shown once.
Uptime Basics API v1
Monitoring data that fits your workflow.
Read monitor health, investigate incidents, control selected monitors, and receive signed events without sharing an account password or exposing dashboard credentials.
Checking API status
$ curl https://api.uptimebasics.com/v1/monitors \ -H "Authorization: Bearer $UPTIME_API_TOKEN" { "data": [ { "id": "mon_example", "status": "up" } ], "pagination": { "nextCursor": null } }
Start with least privilege
From token to verified event.
The quickstart follows the same secure path used in production: a restricted token, bounded requests, idempotent changes, and signature verification over the original webhook body.
Read monitor health
List monitors and follow opaque cursors without making one request per monitor.
Control a test monitor
Pause safely with a unique idempotency key, then activate when your test is complete.
Receive signed events
Filter events by monitor and verify HMAC signatures before processing payloads.
Handle limits predictably
Use response headers, timeouts, retries, and backoff instead of assuming unlimited capacity.
Track contract changes
Follow API and webhook changes with a stable v1 contract and a published deprecation policy.
Developer resources
Everything needed to ship.
Interactive reference
Search every production v1 operation, inspect parameters, required scopes, and response contracts.
Language examples
Copy safe examples for curl, JavaScript, Python, PHP, and PowerShell using placeholders only.
Webhook verification
Validate timestamps and signatures with constant-time comparison and rotation support.
Production boundaries
Secure by default, explicit by design.
Customer tokens are separate from login sessions, secret values are shown once, write operations are idempotent, and permanent monitor deletion is not exposed through the public API.