Skip to Content
Manage ResourcesDestinations

Destinations

Destinations are reusable outbound delivery targets for Chirpier alerts.

Destinations API
See the exact destination routes, supported channels, scope rules, and test-send behavior.
Alert Deliveries
Read the delivery-history and alert transition reference alongside destination setup.

Supported types

  • email
  • webhook
  • slack
  • discord
  • telegram

Routing model

Destinations can be filtered by:

  • policy_ids

This lets you create broad workspace-level routes or tighter routes for specific events and agent workflows.

Common examples

Slack destination:

{
  "url": "https://hooks.slack.com/services/T000/B000/secret",
  "channel": "slack",
  "enabled": true
}

Telegram bot:

{
  "type": "telegram",
  "enabled": true,
  "credentials": {
    "bot_token": "123456:telegram-bot-token",
    "chat_id": "987654321"
  }
}

Destination APIs

  • POST /v1.0/destinations
  • GET /v1.0/destinations
  • GET /v1.0/destinations/:destinationID
  • PUT /v1.0/destinations/:destinationID
  • POST /v1.0/destinations/:destinationID/test

Testing a destination creates test delivery history, which you can inspect from the related alert context with kind=test.

Last updated on
AlertsOverview