Reports the real-time health of the staging environment and its core components.
Dashboard
Dashboard: live visual view of component status and recent incidents.
API Request
curl -X GET 'https://livecheck.stage.waltrex.io/api/v1/status'Response schema
| Field | Type | Description |
|---|---|---|
| name | string | Name of the status report |
| environment | string | Environment this report reflects (stage) |
| status | string | Overall rollup status accross all components |
| generatedAt | string (ISO 8601) | Timestamp when this report was generated |
| validUntil | string (ISO 8601) | How long this result is valid/cacheable before it's considered stale |
| components | array | Per-component health breackdown |
| incidents | array | Recent and active incidents |
Component object
Each entry in components describes one monitored piece of the stage environment.
| Field | Type | Description |
|---|---|---|
| slug | string | Stable identifier for the component (api, wallets, webhooks) |
| name | string | Display name (Stage API, Stage Wallets, Stage Webhooks) |
| status | string | Component-level status (operational, outage) |
| checkedAt | string (ISO 8601) | Timestamp of the last health check |
| latencyMS | number | Response latency (ms) of the underlying check |
| reason | string | Short/code message explaining the status ("ok" when healthy, otherwise an error reason) |
Incident object
Each entry in incidents describes a past or ongoing disruption.
| Field | Type | Description |
|---|---|---|
| id | number | Unique incident ID |
| component | string | slug of the affected component (api, wallets, webhooks) |
| title | string | Short description of the incident |
| severity | string | Security level (e.g. outrage) |
| status | string | Current state of the incident (e.g. resolved, investigating, ongoing) |
| createdAt | string (ISO 8601) | When the incident was opened |
| resolvedAt | string (ISO 8601) | null | When the incident was resolved, if applicable |
Caching behaviorConsumers should treat the report as valid until validUntil and avoid polling more frequently than that window to reduce load.
Example response
{
"name": "Waltrex Stage Status",
"environment": "stage",
"status": "operational",
"generatedAt": "YYYY-MM-DDTHH:mm:ss.sssZ",
"validUntil": "YYYY-MM-DDTHH:mm:ss.sssZ",
"components": [
{
"slug": "api",
"name": "Stage API",
"status": "operational",
"checkedAt": "YYYY-MM-DDTHH:mm:ss.sssZ",
"latencyMs": 89,
"reason": "ok"
},
{
"slug": "wallets",
"name": "Stage Wallets",
"status": "operational",
"checkedAt": "YYYY-MM-DDTHH:mm:ss.sssZ",
"latencyMs": 113,
"reason": "ok"
},
{
"slug": "webhooks",
"name": "Stage Webhooks",
"status": "operational",
"checkedAt": "YYYY-MM-DDTHH:mm:ss.sssZ",
"latencyMs": 110,
"reason": "ok"
}
],
"incidents": [
{
"id": 9,
"component": "webhooks",
"title": "Service disruption: Stage Webhooks",
"severity": "outage",
"status": "resolved",
"createdAt": "YYYY-MM-DDTHH:mm:ss.sssZ",
"resolvedAt": "YYYY-MM-DDTHH:mm:ss.sssZ"
}
]
}