> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/integrations/deployments-and-incidents/incident-api.md).

# Incident API

Submit incident data to Hivel to calculate critical reliability metrics: Change Failure Rate (CFR) and Mean Time to Recovery (MTTR). Choose where your incident data is sent based on your Hivel deployment model.

#### Overview

Incident data captures when issues occur and how quickly your team resolves them. Hivel processes this information to calculate reliability metrics that measure your team's incident response and recovery performance.

#### Choose Your Connection Method

**Hivel-Managed (Default)**

**Use this if:** You use Hivel's hosted platform.

Send incident data directly to Hivel's cloud platform:

* **Endpoint:** `app.hivel.ai` (global) or `app.hivel.in` (India region)
* **Data:** Incidents are received and processed by Hivel's servers
* **Best for:** Organizations using Hivel's standard SaaS offering

{% content-ref url="/pages/LQ3vbIUfQIf8fwYpMo6i" %}
[Hivel-managed](/integrations/deployments-and-incidents/incident-api/hivel-managed.md)
{% endcontent-ref %}

**Self-Hosted**

**Use this if:** You run Hivel's on-premises deployment.

Send incident data to a webhook gateway running on your own infrastructure. Incidents remain within your network before reaching your Hivel instance.

* **Deployment:** Webhook gateway runs entirely on your infrastructure
* **Data:** Incidents stay on your network - no external transmission before internal delivery
* **Best for:** Organizations with on-premises or self-managed Hivel deployments requiring data residency control

{% content-ref url="/pages/3tWVp21copHozIAMf4j4" %}
[On-Premises](/integrations/deployments-and-incidents/incident-api/on-premises.md)
{% endcontent-ref %}