Upload a new incident to the system. Token must have ‘Manage Events’ permission. System will only upload incident once, using the sysId to prevent duplicates. Important: Do NOT include the ‘id’ field in your request - use ‘sysId’ to identify incidents from your source system. By default, timestamps are assumed to be in UTC and will be converted to the tenant’s local timezone. Set convertFromUtc=false if your timestamps are already in local time.
Incident data transfer object for creating or updating incidents
Unique system identifier from your source CAD system. This is used to prevent duplicate incidents.
"INC-2026-001234"
Incident number or call sign displayed to users
"26-001234"
Incident type / problem nature / call type classification
"Medical Emergency - Cardiac Arrest"
Date and time when the incident was created in the CAD system. Subject to timezone conversion based on convertFromUtc parameter (defaults to UTC). Used as fallback for callPickupTime/callReceivedTime if those are missing.
"2026-01-06T10:25:00Z"
The personnel ID of the call taker. This field gets mapped to the user's Personnel ID in the system to associate users with events
"CT-456"
Timestamp when the incident was closed in the CAD system. Subject to timezone conversion (defaults to UTC).
"2026-01-06T11:45:00Z"
Case report number if assigned to the incident
"CR-2026-9876"
Priority level of the incident as assigned by CAD
"Priority 1"
The primary caller's phone number
"555-123-4567"
The primary caller's name
"John Smith"
Agency identifier responding to or handling the incident
"CITY-FIRE-01"
Type of agency (e.g., Fire, Police, EMS, Aeromedical)
"Fire"
Timestamp when the incident was added to the dispatch queue. Subject to timezone conversion based on convertFromUtc parameter (defaults to UTC).
"2026-01-06T10:30:00Z"
Final disposition or outcome of the incident
"Transport to Hospital"
Address or location description of the incident
123
Latitude coordinate of the incident location (decimal degrees)
40.7128
Longitude coordinate of the incident location (decimal degrees)
-74.006
The position/workstation that the call taker who received the call was sitting in. Used for call audio matching and analytics.
"Position-01"
Name of the call taker who handled the incident
"Jane Doe"
Information about how the incident was initiated. Typically indicates channels such as Admin Line, E911, Field Initiated, etc.
"E911"
Initial incident type as reported when call was first received. May differ from final incidentType if call was reclassified.
"Chest Pain"
Additional context, comments, or narrative about the incident
"Caller reports patient experiencing chest pain and shortness of breath for 30 minutes"
Geographic response area, jurisdiction, beat, or ORI code. Used for routing and organizational purposes.
"Beat-3-Downtown"
Radio channel assigned for communications on this incident
"FIRE-TAC-1"
Time the call was received by the system. Required for matching call audio. Subject to timezone conversion (defaults to UTC). If both callReceivedTime and callPickupTime are missing, both will be populated from incidentDate. Can be the earliest timestamp indicating the call taker has begun creating a CAD incident.
"2026-01-06T10:23:00Z"
Time the call was answered/picked up. Required for matching call audio. Subject to timezone conversion (defaults to UTC). If not provided, this will be auto-populated from callReceivedTime if available, otherwise from incidentDate if both callPickupTime and callReceivedTime are missing. Can be the earliest timestamp indicating the call taker has begun creating a CAD incident.
"2026-01-06T10:23:15Z"
Time the call ended/hung up. Required for matching call audio. Subject to timezone conversion (defaults to UTC).
"2026-01-06T10:28:00Z"
List of notes/comments associated with the incident. Timestamps are subject to timezone conversion.
List of responders/units assigned to the incident. Timestamps are subject to timezone conversion.
System ID (sysId) of a related or parent incident for linking incidents together. Used to establish relationships between incidents (e.g., duplicate calls, related events).
"INC-2026-001233"
OK