REST API
Manage your monitoring workspace over HTTPS with bearer API keys.
Build around your monitoring data
The Upty REST API supports monitor management, groups, notification channels, status pages, maintenance and reports. Use it from a server-side integration or script. Account sign-in, billing and administration are separate from this public API.
Your first request
List your monitors with curl, JavaScript or Python.
Keys & authentication
Understand scopes, tokens and workspace access.
Monitor workflows
Create, inspect, pause and update monitors.
Other resources
Groups, status pages, maintenance, channels and reports.
Errors & limits
Handle validation, permissions, rate limits and retries.
Endpoint reference
Browse every operation in the public API contract.
Request schemas
Field types, required values, limits and defaults.
Base URL and request format
https://upty.io/apiSend JSON with Content-Type: application/json when an operation accepts a body. Responses are normally JSON, except for documented downloads and operations that return no content. Do not attach a body to a request that does not define one.
Choose the right credential
Workspace API keys start with upk_. Create a key in Integration & API. Start with a read-only key for dashboards or reporting. Log-ingestion tokens, host tokens and heartbeat addresses are different credentials with different purposes.
The API contract
The public OpenAPI document describes operations and request schemas. The endpoint reference below is a readable snapshot of that contract. No live requests are executed by these documentation pages.
Some features require a particular plan or account access. Workspace membership does not automatically grant every operation. Check access and ownership before building an automated workflow.
Start with one read request
curl --fail-with-body "https://upty.io/api/monitors" \
-H "Authorization: Bearer $UPTIVA_API_KEY"See Quickstart for complete examples with error handling, or go directly to the endpoint reference.