team_id in the path and submitting incident details in the request body. Required fields include the name of the incident, a brief description, and its urgency level (e.g., low, medium, high).This endpoint is used for manually creating incidents that are not triggered by automated rulesets — such as those reported by users, detected through manual testing, or raised in response to unmonitored issues.
Use cases:
- Manual incident reporting — Log issues discovered by team members or reported externally that require structured follow-up.
- Internal escalation — Create incidents as part of internal workflows when external events do not automatically trigger them.
- Incident simulation or testing — Manually trigger test scenarios to verify response automation, notifications, and rule behavior.
To track actions taken on this incident, use the Retrieve Incident Actions endpoint. Need to make changes later? Use the Update Incident endpoint.
Authorization: Bearer YOUR_TOKEN
Expected Behavior:
- On success, the system will create a new incident and return the incident ID.
- If the request is invalid, the system will return an error message with details of the invalid fields.