This guide covers how to use the Status Data API to track the health of services your applications depend on. For conceptual background, see Status Data overview .
Browse the service catalog
List available services:
devhelm status-data services list
Filter by category:
curl "https://api.devhelm.io/api/v1/services?category=cloud-infrastructure&limit=20"
Get a specific service by slug:
curl https://api.devhelm.io/api/v1/services/github
Add service dependencies
Add services you depend on so DevHelm notifies you when their status changes:
curl -X POST https://api.devhelm.io/api/v1/service-subscriptions/github \
-H "Authorization: Bearer $DEVHELM_API_TOKEN "
Dependencies connect the Status Data system to your notification policies. When a tracked service has an incident, DevHelm evaluates your policies and alerts through configured channels.
Free plans support up to 10 service dependencies. Paid plans have unlimited dependencies.
Query uptime data
Get historical uptime for a service:
curl "https://api.devhelm.io/api/v1/services/github/uptime?period=30d&granularity=daily" \
-H "Authorization: Bearer $DEVHELM_API_TOKEN "
Response includes overall uptime percentage and time-bucketed data:
{
"overallUptimePct" : 99.95 ,
"period" : "30d" ,
"granularity" : "daily" ,
"buckets" : [
{ "timestamp" : "2026-04-01T00:00:00Z" , "uptimePct" : 100.0 },
{ "timestamp" : "2026-04-02T00:00:00Z" , "uptimePct" : 99.8 }
]
}
Available periods and granularity
Period Description Allowed granularity 24hLast 24 hours hourly, daily7dLast 7 days hourly, daily30dLast 30 days hourly, daily, monthly90dLast 90 days hourly, daily, monthly1yLast year daily, monthly2yLast 2 years daily, monthlyallAll history daily, monthly
View components
Services break down into components (e.g., API, dashboard, CDN):
curl https://api.devhelm.io/api/v1/services/github/components
Get uptime for a specific component:
curl "https://api.devhelm.io/api/v1/services/github/components/<component-id>/uptime?period=30d"
Track incidents
List incidents for a service:
# Active incidents
curl "https://api.devhelm.io/api/v1/services/github/incidents?status=active"
# Resolved incidents
curl "https://api.devhelm.io/api/v1/services/github/incidents?status=resolved"
# Cross-service incidents
curl "https://api.devhelm.io/api/v1/services/incidents?status=active"
Get incident details with timeline:
curl https://api.devhelm.io/api/v1/services/github/incidents/ < incident-i d >
View maintenance windows
Check scheduled maintenance for a service:
curl https://api.devhelm.io/api/v1/services/github/maintenances
Resource groups
Group related monitors and services together for aggregate health tracking:
# Create a resource group
curl -X POST https://api.devhelm.io/api/v1/resource-groups \
-H "Authorization: Bearer $DEVHELM_API_TOKEN " \
-H "Content-Type: application/json" \
-d '{
"name": "Payment Stack",
"description": "All payment-related monitors and services"
}'
# Add members
curl -X POST https://api.devhelm.io/api/v1/resource-groups/ < group-i d > /members \
-H "Authorization: Bearer $DEVHELM_API_TOKEN " \
-H "Content-Type: application/json" \
-d '{
"memberType": "monitor",
"memberId": "<monitor-id>"
}'
Resource groups aggregate health across monitors and services, and can suppress member-level alerts when a group-level incident is active.
Next steps
Alerting guide Configure notifications for status data incidents.
API Reference Full Status Data API endpoint reference.