---
title: "CreateHTTP Alert Events V2"
method: POST
path: "/v2/alert_events/http/{alert_source_config_id}"
tags: ["Alert Events V2"]
---

# CreateHTTP Alert Events V2

`POST /v2/alert_events/http/{alert_source_config_id}`

Create an alert event using an HTTP source.

## Path parameters

- `alert_source_config_id` string, required

## Query parameters

- `token` string

## Headers

- `authorization` string

## Request body

- AlertEventsV2CreateHTTPRequestBody
  - `deduplication_key` string — A deduplication key can be provided to uniquely reference this alert from your alert source. If you send an event with the same deduplication_key multiple times, only one alert will be created in incident.io for this alert source config.
  - `description` string — Description that optionally adds more detail to title. Supports markdown.
  - `metadata` object — Any additional metadata that you've configured your alert source to parse
  - `source_url` string — If applicable, a link to the alert in the upstream system
  - `status` 'firing' | 'resolved', required — Current status of this alert
  - `title` string, required — Alert title which is used when summarising the alert

## Response `202`

Accepted response.

- AlertResult
  - `deduplication_key` string, required — The deduplication key that the event has been processed with
  - `message` string, required — Human readable message giving detail about the event
  - `status` string, required — Status of the event

---

[API](https://skmtc.net/incident/apis/incident-io.md) · [All operations](https://skmtc.net/incident/apis/incident-io/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/incident/incident-io/revisions/602fc25ddd76/schema)