v1
latestOpenAPI 3.1.02026-07-263911,4691.1 MBCreate Issue
Request body
Optional. The unique identifier of the incident If not provided, UUID will be generated server side
Required. Title of the incident Title is limited to only 255 characters max
Optional. Date and time this incident was created
Required. ID of the incident's category If not set, this incident will be stored with the default category(None)
Optional. An array of all, if any, custom questions that have been answered by the contributor @deprecated: Use QuestionAnswer instead. This was a field used for string custom questions. We've since moved to structured custom questions in the QuestionAnswer field.
Optional. The email address of the contributor
Optional. ID of the site to associate with the incident. If not provided, no site will be associated with the incident.
Optional. The name of the contributor
Optional. The contact details of the contributor
Optional. The access token used to authenticate the request. This field should be set when following the contributor flow. Otherwise, authenticate via normal means.
Optional. Description of the issue (maximum 500 characters).
Optional. Date and time this incident occurred at
Optional. The ID of the asset associated with this incident.
Optional. True when this issue was created via an AI-assisted flow (e.g. the QR-code AI Issue Creation flow seeded by GenerateIncidentStream). The client declares AI involvement; the server persists the flag and surfaces it on Incident.ai_generated. Top-level marker for EU AI Act Article 50(2) machine-readable detectability (AI-522). Per-field origin tracking is intentionally out of scope for iteration 1 — see the EU AI Act compliance DACI.
Response
A successful response.
The UUID of the incident that was created.
The unique id of the incident that was created. Formatted like: IS-1234.