> ## Documentation Index > Fetch the complete documentation index at: https://docs.devhelm.io/llms.txt > Use this file to discover all available pages before exploring further. # One-day rollup for a service: aggregated uptime, per-component impacts, and overlapping incidents > Powers the click/hover-to-expand panel under each uptime bar on the public status page. Single round-trip — components, sums, and overlapping incidents (with affected component names) are returned in one response. ## OpenAPI ````yaml /openapi/monitoring-api.json get /api/v1/services/{slugOrId}/days/{date} openapi: 3.0.1 info: title: DevHelm API description: >- DevHelm monitoring and incident management API. Create and manage uptime monitors, incidents, alert channels, notification policies, and more. version: '1.0' contact: name: DevHelm url: https://devhelm.io email: support@devhelm.io servers: - url: https://api.devhelm.io description: Production security: - BearerAuth: [] tags: - name: Alert Channels description: Alert channel CRUD and connectivity testing - name: Alert Deliveries description: 'Delivery audit trail: inspect per-attempt details for alert deliveries' - name: API Auth description: Identity and quota info for API key authentication - name: API Keys description: Organization API key management - name: Audit Log description: Organization audit trail - name: Check Results description: Query raw check results, uptime statistics, and summary data - name: Dashboard description: Overview dashboard aggregates - name: Deploy Lock description: Mutex for CLI deploy operations - name: Environments description: Variable namespace management for monitors - name: Forensics description: >- Detection engine event-sourced history (policy snapshots, rule evaluations, state transitions) - name: Heartbeat description: Public ping endpoint for heartbeat monitors - name: Incident Policies description: Manage trigger, confirmation, and recovery rules for monitors - name: Incidents description: Incident management and lifecycle - name: Integrations description: Static catalog of supported alert channel integrations - name: Invites description: Organization invite management - name: Maintenance Windows description: Schedule alert-suppression windows for monitors - name: Members description: Organization member management - name: Monitor Alert Channels description: Manage alert channel mappings for a monitor - name: Monitor Assertions description: Manage assertions for a monitor - name: Monitor Auth description: Manage authentication configuration for a monitor - name: Monitors description: Monitor CRUD and lifecycle management - name: Notification Dispatches description: >- Dispatch debugging API: inspect which policies matched an incident and track delivery status - name: Notification Policies description: Org-level notification routing policies with JSONB match rules - name: Notifications description: In-app notification center - name: Organizations description: Organization management - name: Resource Groups description: Resource group CRUD and member management - name: Secrets description: Organization environment secret management - name: Service Subscriptions description: Manage which services an organization tracks - name: Status Data description: Public service status catalog, components, uptime, and incident history - name: Status Pages description: Status page management - name: Tags description: Org-scoped tag management for monitors - name: Vault description: Organization vault management (admin-only) - name: Webhooks description: Webhook endpoint management, event catalog, and delivery history - name: Workspaces description: Workspace management within an organization paths: /api/v1/services/{slugOrId}/days/{date}: get: tags: - Status Data summary: >- One-day rollup for a service: aggregated uptime, per-component impacts, and overlapping incidents description: >- Powers the click/hover-to-expand panel under each uptime bar on the public status page. Single round-trip — components, sums, and overlapping incidents (with affected component names) are returned in one response. operationId: getServiceDayDetail parameters: - name: slugOrId in: path required: true schema: type: string - name: date in: path description: UTC calendar day in ISO format (YYYY-MM-DD) required: true schema: type: string format: date responses: '200': description: OK content: '*/*': schema: $ref: '#/components/schemas/SingleValueResponseServiceDayDetailDto' '400': description: Bad request — the payload failed validation content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized — missing or invalid credentials content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Forbidden — the actor lacks permission for this resource content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Not found — the requested resource does not exist content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: Conflict — the request collides with current resource state content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Internal server error — see the message field for details content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '502': description: Bad gateway — an upstream provider returned an error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '503': description: Service unavailable — try again shortly content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: SingleValueResponseServiceDayDetailDto: required: - data type: object properties: data: $ref: '#/components/schemas/ServiceDayDetailDto' ErrorResponse: required: - code - message - status - timestamp type: object properties: status: type: integer description: HTTP status code (mirrors the response status line) format: int32 example: 404 code: type: string description: >- Coarse machine-readable error category (e.g. NOT_FOUND, RATE_LIMITED); stable per status example: NOT_FOUND message: type: string description: Human-readable error message; safe to surface to end users example: Monitor not found timestamp: type: integer description: Server time when the error was produced (epoch milliseconds) format: int64 example: 1737302400000 requestId: type: string description: >- Opaque per-request id; same value as the X-Request-Id response header. Use in support tickets. nullable: true example: 5b6f7a8c-1234-4d5e-9f0a-1b2c3d4e5f6a errors: type: array description: >- Structured per-field rejections; populated for validation errors, null otherwise nullable: true items: nullable: true allOf: - $ref: '#/components/schemas/ErrorEntry' description: Uniform error envelope returned for every non-2xx response example: status: 404 code: NOT_FOUND message: Monitor not found timestamp: 1737302400000 requestId: 5b6f7a8c-1234-4d5e-9f0a-1b2c3d4e5f6a ServiceDayDetailDto: required: - components - date - incidents - totalPartialOutageSeconds - totalMajorOutageSeconds - totalDegradedSeconds type: object properties: date: type: string description: UTC calendar day this rollup covers format: date overallUptimePercentage: type: number description: >- Average uptime % across leaf components with uptime data; null if no data format: double nullable: true totalPartialOutageSeconds: type: integer description: Sum of partial outage seconds across all leaf components format: int64 totalMajorOutageSeconds: type: integer description: Sum of major outage seconds across all leaf components format: int64 totalDegradedSeconds: type: integer description: Sum of degraded performance seconds across all leaf components format: int64 components: type: array description: >- Per-component impact rows for the day (only components with uptime data) items: $ref: '#/components/schemas/ComponentImpact' incidents: type: array description: >- Incidents that were active at any point during this day (started before day end, resolved after day start) items: $ref: '#/components/schemas/DayIncident' description: >- One-day rollup for a public service status page: aggregated uptime, per-component impact, and incidents that overlapped the day. Powers the click/hover-to-expand panel under each uptime bar. ErrorEntry: required: - code - message type: object properties: code: minLength: 1 type: string description: >- Stable machine-readable code; see ValidationErrorCode for the registry example: MONITOR_HEARTBEAT_GRACE_EXCEEDS_INTERVAL field: type: string description: >- JSON-pointer-like path to the offending field, or null for request-wide errors nullable: true example: config.gracePeriod message: minLength: 1 type: string description: Human-readable message; safe to surface to end users description: One structured validation rejection ComponentImpact: required: - componentId - componentName - uptimePercentage - partialOutageSeconds - majorOutageSeconds type: object properties: componentId: type: string description: Status page component UUID format: uuid componentName: type: string description: Component display name groupName: type: string description: Parent group display name when the component belongs to a group nullable: true uptimePercentage: type: number description: Computed uptime % for this component on this day format: double partialOutageSeconds: type: integer description: Seconds of partial outage observed on this day format: int32 majorOutageSeconds: type: integer description: Seconds of major outage observed on this day format: int32 description: One component's uptime contribution for the day DayIncident: required: - affectedComponentNames - id - impact - status - title - scheduled type: object properties: id: type: string description: Status page incident UUID format: uuid title: type: string description: Incident title status: type: string description: >- Lifecycle status (investigating, identified, monitoring, resolved, …) enum: - INVESTIGATING - IDENTIFIED - MONITORING - RESOLVED impact: type: string description: Severity bucket (none, minor, major, critical) enum: - NONE - MINOR - MAJOR - CRITICAL scheduled: type: boolean description: True for scheduled maintenances; false for unplanned incidents startedAt: type: string description: Incident start timestamp format: date-time nullable: true resolvedAt: type: string description: Incident resolved timestamp; null while still active format: date-time nullable: true affectedComponentNames: type: array description: Display names of components affected by this incident (deduplicated) items: type: string description: >- Display names of components affected by this incident (deduplicated) description: Incident that overlapped the day securitySchemes: BearerAuth: type: http description: API key (dh_live_...) or Auth0 JWT token scheme: bearer bearerFormat: JWT ````