Health & Status
Check whether AlexWeb is ready, read its uptime, and measure response time.
GET
Read service status and uptime
Service monitoring
These requests are public. They do not require an API key, and the responses contain no private account data or internal infrastructure addresses.
Use health checks to decide whether a service can handle work. Use status to understand its readiness and uptime at the time of your request.
Try it
Send the request in this page’s interactive panel, or use cURL:What you’ll see
This is an illustrative response; uptime and timings change with each request.
The status response checks the API process and its storage. It does not test every webhook receiver, OAuth callback, or connected Home Assistant instance.
Health checks
Readiness
GET /api/v1/health verifies a storage read. Use this when deciding whether the API is ready to serve requests.Liveness
GET /health confirms that the API process can answer HTTP. It remains available for existing monitors./api/v1/health returns HTTP 503 and:
/api/v1/status also returns 503 when degraded. Use the HTTP status code in your monitor, and inspect the JSON to understand the result. A liveness response alone does not prove storage is ready.
Understand the timing
Storage latency is one small operation inside the API. It excludes the time spent reaching the service over the internet. Client response time includes the network path and the time it takes to receive a response. You can measure it with cURL:Use it in a monitor
- Point your monitor at
https://api.alexxweb.com/api/v1/health. - Treat HTTP 200 as ready and 503 as unavailable.
- Use a reasonable interval, such as once per minute, and confirm repeated failures before alerting.
- Keep the
X-Request-Idheader from failed checks when requesting help.
Other requests
For request counts, error rates, and latency statistics belonging to your account, use Usage & Limits.