Health Checks
Monitor the status of RTObase services using built-in health check endpoints.
Last updated 3 Sept 2026
RTObase provides health check endpoints for both the backoffice and web applications. These endpoints can be used by uptime monitors, load balancers, and deployment pipelines to verify that the services are running correctly.
Endpoints
Each application exposes a health check at /api/health:
| App | URL |
|---|---|
| Backoffice | https://<backoffice-domain>/api/health |
| Web | https://<web-domain>/api/health |
No authentication is required. Both endpoints respond to GET requests. The HTTP status code follows the overall status: 200 when status is ok, 503 when it is degraded. A monitor that only checks the status code still sees a failure.
Response format
{
"status": "ok",
"timestamp": "2026-02-08T03:00:00.000Z",
"app": "backoffice",
"checks": {
"database": {
"status": "ok",
"latencyMs": 12
}
}
}
Fields
| Field | Description |
|---|---|
| status | Overall health: ok when all checks pass, degraded if any fail |
| timestamp | ISO 8601 timestamp of the check |
| app | Which application responded (backoffice or web) |
| checks.database.status | Database connectivity: ok or error |
| checks.database.latencyMs | Round-trip time to the database in milliseconds |
Note
The response deliberately carries no diagnostic detail beyond these fields. Because the endpoint is unauthenticated, a failing check reports only that it failed; the underlying reason is recorded in our internal logs.
What is checked
Database
The health check verifies that the application can reach its database by executing a lightweight query. If the database is unreachable or misconfigured, the check reports error.
Using health checks
Uptime monitoring
Point an uptime monitor (e.g. UptimeRobot, Better Uptime, Pingdom) at the /api/health endpoint for each app. Alert on any non-200 response; the status field in the body is degraded in that case.
Load balancers
Configure your load balancer or reverse proxy to poll /api/health and remove unhealthy instances from the pool.
Deployment verification
After deploying a new version, call the health check endpoint to confirm the application started successfully and can reach the database.
Troubleshooting
| Symptom | Possible cause |
|---|---|
status: "degraded" (HTTP 503) | The application cannot reach its database. Contact support with the timestamp from the response |
High latencyMs values | The database is under load, or there is network latency between the application and the database |
| Endpoint not responding | The application process has crashed or is not running |