Email and Slack

An alert delivers to its destinations. Email is the zero-setup option; Slack puts hits where the team already is.

Email

curl -X POST -H "Authorization: Bearer $SPUTNIK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"email": "you@example.com"}' \
  "https://sputnikintelligence.com/api/v1/alerts/<alert-slug>/destinations"

Any address, not only team members' — a shared inbox, or a client who wants coverage directly. Add several to one alert if several people need it.

Each email carries the post, which search matched, and the snippet, so it is forwardable as it stands.

Slack

Slack goes through an incoming webhook, registered once for your team and reusable by any alert.

In Slack, create an incoming webhook for the channel you want. Then register it here with channel: "slack":

curl -X POST -H "Authorization: Bearer $SPUTNIK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
        "name": "#coverage",
        "url": "https://hooks.slack.com/services/...",
        "channel": "slack"
      }' \
  "https://sputnikintelligence.com/api/v1/webhooks"

Then point an alert at it:

curl -X POST -H "Authorization: Bearer $SPUTNIK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"webhook": "<webhook-slug>"}' \
  "https://sputnikintelligence.com/api/v1/alerts/<alert-slug>/destinations"

Hits arrive as a formatted message with the title, publication, date and snippet, linked through to both the post on Sputnik and the publisher's original.

The channel is fixed by the Slack webhook URL, not by us. To post to a second channel, create a second incoming webhook in Slack and register it separately.

Which to use

Want	Use
Something working in thirty seconds	Email
The team to see it without checking anything	Slack
Hits in your own system	Webhooks
An agent to read them on its own schedule	GET /alert-hits

These are not exclusive. One alert can deliver to an inbox, a Slack channel and your CRM at once.

If delivery stops

Check is_delivering on the destination. False means the webhook behind it deactivated itself after repeated failures — see Webhooks. Email destinations do not deactivate themselves, so a silent email alert is usually a quiet week or a spam filter.