Delete an alert source

curl -X DELETE http://localhost:5080/api/v1/alerts/sources/$SOURCE_ID \
  -H "authorization: Bearer $MS_TOKEN"

curl -X DELETE http://localhost:5080/api/v1/alerts/sources/$SOURCE_ID \
  -H "authorization: Bearer $MS_TOKEN"

DELETE /api/v1/alerts/sources/{id}

Deletes an alert source. It requires alerts.sources.manage. Its token stops working at once, and its recently received requests go with it. Its open incidents are resolved in the name of the calling user, since without the source they would never receive a recovery. With federation on, the other clusters resolve the source’s open incidents there once the deletion syncs.

curl -X DELETE http://localhost:5080/api/v1/alerts/sources/$SOURCE_ID \
  -H "authorization: Bearer $MS_TOKEN"

On success the answer is 200 with the text deleted. Errors

Status	Cause
`403`	The token lacks `alerts.sources.manage`.
`404`	The source does not exist.

Last modified on October 31, 2026

Overview

Authentication

Intake

Query

APM

RUM

Streams

Alerting

Correlation & Web

Platform & Administration