> ## Documentation Index
> Fetch the complete documentation index at: https://developers.govworx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# CAD integration

> Send incident data to GovWorx, create CAD incidents, and receive incident updates from GovWorx.

# CAD integration

The CAD interface exchanges incident data between a CAD system and GovWorx. It supports two
directions, which GovWorx configures for the agency's integration.

## Send incident data

CAD sends incident data to GovWorx. Send the current incident record when it is created and when
it changes. GovWorx uses the NENA (National Emergency Number Association) Emergency Incident
Data Object (EIDO) standard as its baseline, and also accepts a GovWorx lifecycle event or a
connector-specific format when needed.

<Card title="Submit incident data" icon="arrow-right-to-bracket" href="/connections-platform/inbound-incidents" horizontal>
  Request formats, response behavior, and the API reference for CAD-to-GovWorx submissions.
</Card>

## Create a CAD incident

GovWorx can request that CAD create an incident before a CAD record exists. The request carries
the incident information GovWorx has at that point. CAD and GovWorx then associate the record
with its CAD incident identifier so later updates reach the right incident.

If the identifier is not available during creation, CAD sends an `incident.linked` event after
creation instead. This is a fallback, not the normal association path.

<Card title="Create a CAD incident" icon="square-plus" href="/connections-platform/create-cad-incident" horizontal>
  Creation behavior and the CAD incident association.
</Card>

## Receive incident updates from GovWorx

GovWorx sends updates to a CAD-hosted endpoint. Updates can add information to the CAD record,
or carry data that does not have a CAD incident yet. Call type recommendations, comments,
dispatch recommendations, and completed transcripts are the current update types.

<Card title="Receive incident updates from GovWorx" icon="arrow-right-from-bracket" href="/connections-platform/outbound-interactions" horizontal>
  Endpoint requirements, update types, authentication, and delivery behavior.
</Card>

## Connector profiles

The CAD interface defines the GovWorx baseline. A connector profile records the differences a
specific CAD system requires, such as payload shape, authentication, acknowledgement, or
reliability behavior. It does not create a separate product API.

<Card title="Connector profiles" icon="puzzle-piece" href="/connections-platform/connector-profiles" horizontal>
  How GovWorx documents a CAD-specific compatibility requirement without changing the baseline.
</Card>

## Reference

The CAD API reference contains the complete request, response, webhook, and schema definitions.

<Card title="CAD API reference" icon="book" href="/connections-platform/api-reference/send-incidents-to-govworx/publish-an-incident-event" horizontal>
  Review the contract while implementing the CAD interface.
</Card>