​

Send incident events

CAD sends an incident event when an incident is created or materially changes. Each event contains the complete current incident object. GovWorx compares the event with the existing record and applies the changes. Send events to POST /cad/v1/incidents.

​

Event format

The standard event format is NENA (National Emergency Number Association) Emergency Incident Data Object (EIDO). It identifies the CAD incident and contains the incident’s current state. GovWorx uses this industry-standard format as the baseline rather than requiring a GovWorx-specific incident payload. GovWorx also supports connector-specific formats when a CAD system cannot produce EIDO. A connector profile defines that format and its mapping to the GovWorx incident model.

​

Optional lifecycle signals

Some CAD systems can signal activity before a complete incident record exists. They can send an incident.started event when call taking begins. They can send incident.canceled when the call or incident is canceled. These signals are optional. They do not replace full incident events for normal CAD updates. An incident.linked event is the fallback when CAD creates an incident from a GovWorx update but cannot return its incident identifier in the immediate response. See Create a CAD incident.

​

Response

A successful submission returns 200. GovWorx has validated and stored the event. Processing may continue after the response. The response includes a submissionId, an eventId when the submission produces a normalized incident event, and the GovWorx receipt time. Neither identifier is the CAD incident identifier.

​

Errors

A 400 response means the submission failed schema or connector-configuration validation. A 401 response means the credential is missing or invalid. Errors use the shared ErrorResponse shape. It always includes code and message. It can also include details identifying the invalid field.