Notifications

Add a notification destination and Truto posts to a Slack channel or sends email when your API traffic starts failing, an API token expires or goes stale, a webhook is deactivated, or the monthly usage report is ready.

truto notification-destinations list

Before you start

• One environment per destination. A destination belongs to one environment and is notified about that environment only. With an API token, the destination is created in the token's environment.
• Slack. Create a Slack incoming webhook for the channel you want alerts in and copy its URL.

1. Add a destination

From the console

1. Open Settings → Notifications (app.truto.one/settings/notifications) and pick the environment.
2. Click Add Destination.
3. Fill in the modal:
   • Label — a name for the destination, for example Engineering alerts.
   • Type — Slack or Email. The type can't be changed after the destination is created.
   • For Slack: Webhook URL, and optionally Ignored Status Codes (see API errors).
   • For email: To, and optionally CC, BCC, and Subject Prefix. Separate addresses with commas.
   • Active — whether the destination receives notifications.
   • Event Types — which events to receive. All events is checked by default.
4. Click Create.

From the API

POST /notification-destination creates a destination.

Slack config

Email config

truto notification-destinations create --body '{
  "type": "slack",
  "label": "Engineering alerts",
  "config": {
    "webhook_url": "https://hooks.slack.com/services/T000/B000/XXXX",
    "ignored_status_codes": [401, 404]
  },
  "event_types": ["api_errors", "api_token_events"]
}'

curl -X POST https://api.truto.one/notification-destination \
  -H "Authorization: Bearer <API token>" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "slack",
    "label": "Engineering alerts",
    "config": {
      "webhook_url": "https://hooks.slack.com/services/T000/B000/XXXX",
      "ignored_status_codes": [401, 404]
    },
    "event_types": ["api_errors", "api_token_events"]
  }'

{
  "id": "3b7e2c1a-9f4d-4e8b-a2c6-1d5f7e9a0b34",
  "type": "slack",
  "label": "Engineering alerts",
  "config": {
    "webhook_url": "********",
    "ignored_status_codes": [401, 404]
  },
  "is_active": true,
  "environment_id": "ac15abdc-b38e-47d0-97a2-69194017c199",
  "event_types": ["api_errors", "api_token_events"],
  "created_at": "2026-11-02T10:20:11.000Z",
  "updated_at": "2026-11-02T10:20:11.000Z"
}

An email destination looks like this:

{
  "type": "email",
  "label": "On-call inbox",
  "config": {
    "to": ["oncall@example.com"],
    "cc": ["platform@example.com"],
    "subject_prefix": "[Truto prod]"
  },
  "event_types": ["all"]
}

2. Send a test notification

POST /notification-destination/test sends a test message to one destination, whatever event types it subscribes to. In the console, open the destination's menu and click Send test notification.

truto notification-destinations test --id <destination_id>

curl -X POST https://api.truto.one/notification-destination/test \
  -H "Authorization: Bearer <API token>" \
  -H "Content-Type: application/json" \
  -d '{ "id": "<destination_id>" }'

The endpoint answers {"success": true} once the test has been sent. It doesn't report whether Slack or the mail server accepted it, so check the channel or inbox. In Slack the message reads Event: test with the environment and time; by email the subject is [Truto] Test Notification (or your prefix).

Event types

ignored_status_codes applies to the api_errors digest. The codes from every Slack destination subscribed to API errors in the environment are combined, so ignoring a code on one destination removes it from the environment's digest for all of them.

Changing a destination

PATCH /notification-destination/:id updates a destination. DELETE /notification-destination/:id deletes it. GET /notification-destination lists the environment's destinations and GET /notification-destination/:id reads one.

• config replaces the stored config, except the secret fields: a Slack webhook_url, or email to, cc and bcc. A secret you leave out, or send back as ********, is kept. Send null to clear one.
• event_types replaces the subscribed list when it has at least one entry. An empty list leaves the subscriptions unchanged; send ["all"] to receive everything again.
• is_active: false pauses the destination without deleting it.

truto notification-destinations update <destination_id> \
  --body '{"event_types":["all"],"config":{"ignored_status_codes":[]}}'

curl -X PATCH https://api.truto.one/notification-destination/<destination_id> \
  -H "Authorization: Bearer <API token>" \
  -H "Content-Type: application/json" \
  -d '{ "event_types": ["all"], "config": { "ignored_status_codes": [] } }'

Next

Notifications summarise; for every individual request and sync job event, stream the raw logs to Datadog, Splunk or another tool with Log forwarding. To be told about events in your own app rather than in Slack, use webhooks.