Manually create a new incident and assign responders.
Documentation Index
Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt
Use this file to discover all available pages before exploring further.
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Incidents Manage (on-call) |
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Parameters for manually creating an incident.
Incident severity.
Info, Warning, Critical Incident title, up to 512 characters.
512Incident description, up to 1024 characters.
1024Channel to file the incident into. Optional; leave unset for a standalone incident.
Incident assignment target. Either person_ids or escalate_rule_id must be provided.
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.