Destinations

Destinations allow you to fan out webhook events to multiple systems beyond your primary delivery_url. Use them for alerting, logging, or routing events to additional services.

How Destinations Work

Destinations are triggered after the primary delivery cycle:

• On successful primary delivery (if no condition is set, or the condition matches)
• After exhausted retries when delivery_failed is true (useful for failure alerts)

Each destination can have a condition expression that determines when it fires.

Destination Types

Type	Description
Webhook	POST to any URL, optionally with HMAC signing
Email	Send notifications via Amazon SES
Slack	Send formatted messages to a Slack channel
Discord	Send formatted embeds to a Discord channel

Managing Destinations

Destinations are attached to provider accounts. Use the Destinations API to create and manage them:

# List destinations for an account
curl https://ingest.transyt.com/admin/accounts/{account_id}/destinations \
  -H "X-Admin-Token: YOUR_ADMIN_TOKEN"

# Create a Slack destination
curl -X POST https://ingest.transyt.com/admin/accounts/{account_id}/destinations \
  -H "X-Admin-Token: YOUR_ADMIN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "destination_type": "slack",
    "name": "Slack Alerts",
    "config": {
      "webhook_url": "https://hooks.slack.com/services/T.../B.../xxx"
    },
    "condition": "delivery_failed"
  }'

Ordering

Destinations have a position field that determines the order in which they are evaluated. Lower positions are evaluated first.