> ## 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.

# Receive a call type update

> GovWorx sends this delivery after an authorized internal caller submits
a call-type update. The configured GovWorx connector maps the update
to the destination CAD while preserving its manual override policy. A
retry uses the same delivery ID.




## OpenAPI

````yaml /connections-platform/openapi/cad.yaml webhook callType
openapi: 3.1.0
info:
  title: GovWorx CAD API
  version: 1.0.0
  license:
    name: Proprietary
    identifier: LicenseRef-Proprietary
  summary: CAD incident ingestion and write-back API
  description: >
    The GovWorx CAD API accepts actual or potential incident activity from CAD

    providers. Providers may submit a NENA (National Emergency Number
    Association)

    Emergency Incident Data Object (EIDO), a

    strongly typed GovWorx incident-lifecycle event, or a vendor-native format
    that

    a GovWorx connector maps into EIDO.


    Tenant identity for vendor submissions is resolved from the API key. The

    `tenantId` in an inbound envelope is a cross-check and is never used for

    routing.


    This document presents the GovWorx best-practice baseline. Connector
    profiles

    are compatibility overlays for vendor constraints; they are not separate

    product APIs. A profile may adapt vendor-facing authentication, reliability,

    acknowledgements, field names, or payload shape. Every deviation identifies
    the

    baseline rule, vendor constraint, replacement behavior, compensating
    control,

    and operational impact. The provisioned connector version pins the profile;

    neither callers nor vendors negotiate or downgrade it per request.


    GovWorx delivers CAD updates to a CAD-hosted HTTPS webhook. GovWorx sends an

    update when it has relevant data for an authorized listener. The configured

    connector maps each update into the fields and capabilities supported by the

    destination CAD.


    GovWorx assigns each outbound CAD operation a finite expiration from its

    operation and connector policy, and does not begin or retry work after it.
    The connector profile

    selects a reliability mode for each operation: `durable_idempotent`,

    `bounded_deduplication`, or `non_idempotent`. That mode determines whether
    the

    recipient enforces the expiration, how it remembers delivery IDs, and
    whether

    an ambiguous request may be retried. GovWorx does not claim exactly-once

    delivery. Every idempotent connector profile declares a maximum retry
    horizon

    and minimum delivery-ID retention. The retention period must be at least as

    long as the retry horizon. A count-only cache is opportunistic duplicate

    protection and does not establish that guarantee. Such a connector is
    treated

    as non-idempotent unless it separately guarantees retention through the
    entire

    retry horizon. Every permitted retry uses the same delivery ID and exact raw

    request body; only the signature timestamp and signature change. Eligible

    retries use exponential backoff with jitter and honor `Retry-After` without

    crossing the expiration. Network errors, `429`, and `5xx` are retryable only

    when the selected reliability profile permits another attempt. Other `4xx`

    responses are terminal.
servers: []
security: []
tags:
  - name: Send incidents to GovWorx
    description: Actual or potential incident submissions from CAD providers.
  - name: Receive incident updates from GovWorx
    description: Signed updates delivered by GovWorx to a CAD-hosted HTTPS endpoint.
externalDocs:
  description: Pinned NENA EIDO 1.0.1 normative schema
  url: >-
    https://github.com/NENA911/EIDO-JSON/blob/1ea5750ba2ef4ea3ec5726222e8bf571d68b1d32/Schema/openapi.yaml
paths: {}

````