> ## 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. # Create a manual incident ## OpenAPI ````yaml /openapi/monitoring-api.json post /api/v1/incidents 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/incidents: post: tags: - Incidents summary: Create a manual incident operationId: create_12 requestBody: content: application/json: schema: $ref: '#/components/schemas/CreateManualIncidentRequest' required: true responses: '201': description: Created content: '*/*': schema: $ref: '#/components/schemas/SingleValueResponseIncidentDetailDto' '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: CreateManualIncidentRequest: required: - severity - title type: object properties: title: minLength: 1 type: string description: Short summary of the incident severity: type: string description: 'Incident severity: DOWN, DEGRADED, or MAINTENANCE' enum: - DOWN - DEGRADED - MAINTENANCE monitorId: type: string description: Monitor to associate with this incident format: uuid nullable: true body: type: string description: Detailed description or context for the incident nullable: true SingleValueResponseIncidentDetailDto: required: - data type: object properties: data: $ref: '#/components/schemas/IncidentDetailDto' 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 IncidentDetailDto: required: - incident - updates type: object properties: incident: $ref: '#/components/schemas/IncidentDto' updates: type: array items: $ref: '#/components/schemas/IncidentUpdateDto' statusPageIncidents: type: array nullable: true items: $ref: '#/components/schemas/LinkedStatusPageIncidentDto' 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 IncidentDto: required: - affectedRegions - createdAt - id - severity - source - status - updatedAt - organizationId - reopenCount - statusPageVisible type: object properties: id: type: string description: Unique incident identifier format: uuid monitorId: type: string description: >- Monitor that triggered the incident; null for service or manual incidents format: uuid nullable: true organizationId: type: integer description: Organization this incident belongs to format: int32 source: type: string description: 'Incident origin: MONITOR, SERVICE, or MANUAL' enum: - AUTOMATIC - MANUAL - MONITORS - STATUS_DATA - RESOURCE_GROUP status: type: string description: Current lifecycle status (OPEN, RESOLVED, etc.) enum: - WATCHING - TRIGGERED - CONFIRMED - RESOLVED severity: type: string description: 'Severity level: DOWN, DEGRADED, or MAINTENANCE' enum: - DOWN - DEGRADED - MAINTENANCE title: type: string description: Short summary of the incident; null for auto-generated incidents nullable: true triggeredByRule: type: string description: Human-readable description of the trigger rule that fired nullable: true affectedRegions: type: array description: Probe regions that observed the failure items: type: string description: Probe regions that observed the failure reopenCount: type: integer description: Number of times this incident has been reopened format: int32 createdByUserId: type: integer description: User who created the incident (manual incidents only) format: int32 nullable: true statusPageVisible: type: boolean description: Whether this incident is visible on the status page serviceIncidentId: type: string description: Linked vendor service incident ID; null for monitor incidents format: uuid nullable: true serviceId: type: string description: Linked service catalog ID; null for monitor incidents format: uuid nullable: true externalRef: type: string description: External reference ID (e.g. PagerDuty incident ID) nullable: true affectedComponents: type: array description: Service components affected by this incident nullable: true items: type: string description: Service components affected by this incident shortlink: type: string description: Short URL linking to the incident details nullable: true resolutionReason: type: string description: How the incident was resolved (AUTO_RECOVERED, MANUAL, etc.) nullable: true enum: - MANUAL - AUTO_RECOVERED - AUTO_RESOLVED startedAt: type: string description: Timestamp when the incident was detected or created format: date-time nullable: true confirmedAt: type: string description: >- Timestamp when the incident was confirmed (multi-region confirmation) format: date-time nullable: true resolvedAt: type: string description: Timestamp when the incident was resolved format: date-time nullable: true cooldownUntil: type: string description: Cooldown window end; new incidents suppressed until this time format: date-time nullable: true createdAt: type: string description: Timestamp when the incident record was created format: date-time updatedAt: type: string description: Timestamp when the incident was last updated format: date-time monitorName: type: string description: >- Name of the associated monitor; populated on list responses. Omitted from JSON (undefined to SDKs) on detail responses, treat missing as null. nullable: true serviceName: type: string description: >- Name of the associated service; populated on list responses. Omitted from JSON (undefined to SDKs) on detail responses, treat missing as null. nullable: true serviceSlug: type: string description: >- Slug of the associated service; populated on list responses. Omitted from JSON (undefined to SDKs) on detail responses, treat missing as null. nullable: true monitorType: type: string description: >- Type of the associated monitor; populated on list responses. Omitted from JSON (undefined to SDKs) on detail responses, treat missing as null. nullable: true resourceGroupId: type: string description: Resource group that owns this incident; null when not group-managed format: uuid nullable: true resourceGroupName: type: string description: >- Name of the resource group; populated on list responses. Omitted from JSON (undefined to SDKs) on detail responses, treat missing as null. nullable: true triggeringCheckId: type: string description: >- Scheduler-minted check execution ID whose result confirmed this incident; joins to check_results, rule_evaluations, and incident_state_transitions. Omitted from JSON (undefined to SDKs) when null, treat missing as null. format: uuid nullable: true triggeredByRuleSnapshotHashHex: type: string description: >- Hex SHA-256 of the canonical policy snapshot that fired; combined with triggeredByRuleIndex points to the exact TriggerRule. Omitted from JSON when null, treat missing as null. nullable: true triggeredByRuleIndex: type: integer description: >- Index of the fired rule inside the policy's trigger_rules array. Omitted from JSON when null, treat missing as null. format: int32 nullable: true engineVersion: type: string description: >- Detection engine semver that evaluated the rule. Omitted from JSON when null, treat missing as null. nullable: true description: Incident triggered by a monitor check failure or manual creation IncidentUpdateDto: required: - createdAt - id - incidentId - notifySubscribers type: object properties: id: type: string format: uuid incidentId: type: string format: uuid oldStatus: type: string nullable: true enum: - WATCHING - TRIGGERED - CONFIRMED - RESOLVED newStatus: type: string nullable: true enum: - WATCHING - TRIGGERED - CONFIRMED - RESOLVED body: type: string nullable: true createdBy: type: string nullable: true enum: - SYSTEM - USER notifySubscribers: type: boolean createdAt: type: string format: date-time LinkedStatusPageIncidentDto: required: - id - impact - status - statusPageId - statusPageName - statusPageSlug - title - scheduled type: object properties: id: type: string format: uuid statusPageId: type: string format: uuid statusPageName: type: string statusPageSlug: type: string title: type: string status: type: string enum: - INVESTIGATING - IDENTIFIED - MONITORING - RESOLVED impact: type: string enum: - NONE - MINOR - MAJOR - CRITICAL scheduled: type: boolean publishedAt: type: string format: date-time nullable: true securitySchemes: BearerAuth: type: http description: API key (dh_live_...) or Auth0 JWT token scheme: bearer bearerFormat: JWT ````