Skip to main content
POST
/
api
/
v1
/
alert-channels
Create alert channel
curl --request POST \
  --url https://app.larm.dev/api/v1/alert-channels \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "<string>",
  "type": "<string>",
  "config": {},
  "enabled": true,
  "default_for_new_monitors": true
}
'
{
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "name": "Engineering Slack",
    "type": "slack",
    "enabled": true,
    "default_for_new_monitors": true,
    "broken_at": null,
    "broken_reason": null,
    "inserted_at": "2025-03-01T12:00:00Z",
    "updated_at": "2025-03-01T12:00:00Z"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.larm.dev/llms.txt

Use this file to discover all available pages before exploring further.

Requires alert_channels:read_write permission.
​
name
string
required
Channel name (1–255 characters)
​
type
string
required
slack, discord, email, webhook, pagerduty, teams, grafana_irm, ilert, incident_io, mattermost, pushover, ntfy, telegram, or sms
​
config
object
required
Type-specific configuration. See Alert channels for fields per type.
​
enabled
boolean
default:true
Whether the channel is active
​
default_for_new_monitors
boolean
default:true
Automatically link to newly created monitors
{
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "name": "Engineering Slack",
    "type": "slack",
    "enabled": true,
    "default_for_new_monitors": true,
    "broken_at": null,
    "broken_reason": null,
    "inserted_at": "2025-03-01T12:00:00Z",
    "updated_at": "2025-03-01T12:00:00Z"
  }
}