API change alerts, posted right into Slack.
Connect your Slack workspace, pick a channel, and Dovkie posts the moment a third-party API you depend on changes — with a severity label so you can spot the breaking ones at a glance.
Installing requires a Dovkie account — we'll prompt you to sign in if you're not already.
Built to be the channel your team will actually keep.
Severity-aware, channel-aware, and quiet until it matters.
Quiet by default
Every alert is AI-classified Breaking, Deprecation, Additive, or Informational. Route only what you want to see — most teams keep Breaking and Deprecation.
Per-channel routing
Send different APIs to different channels. Stripe goes to #payments, Auth0 to #security, the rest to #api-watch. One workspace install, as many channels as you need.
Public or private channels
Posts to any public channel out of the box. For private channels, invite the Dovkie bot with /invite @Dovkie — same alerts, same look.
Three clicks from install to first alert.
No webhook URL to copy, no proxy to maintain.
- 1
Add to Slack
Click the button, approve the install in Slack. We ask for the minimum scopes — no message reading, no file access.
- 2
Pick a channel
Choose where alerts should land from the dropdown of channels Dovkie can post to. Switching channels later is one delete + add away.
- 3
Wire up an alert rule
Tell Dovkie which APIs to watch and which severities you care about. The next time something changes, you'll hear about it in Slack.
What we ask for, and what we don't.
We request the smallest scope set that lets Dovkie post an alert and show you a channel picker. Nothing more.
chat:writePost the alert messages into the channel you select.
channels:readRead the names of public channels — just so we can show you a picker after install.
groups:readSame as above, for private channels the Dovkie bot has been invited into.
team:readRead your workspace name so the connector reads as "#general — Acme" in the Dovkie UI instead of an opaque id.
Dovkie never reads messages, downloads files, sends DMs, or stores anything from your workspace beyond what's listed above. Bot tokens are encrypted at rest and decrypted only at the moment a message is posted.
Frequently asked questions
- What if I install the wrong workspace?
- Open Slack, go to Apps, find Dovkie, and Remove App. Then click Add to Slack again from this page — the reinstall replaces the previous setup.
- Does the bot need to be added to every channel?
- For public channels, no — Slack lets the bot post once installed. For private channels, invite the bot with /invite @Dovkie. Same for shared channels.
- How do I disconnect?
- Either delete the connector inside Dovkie or remove the app from Slack. Both stop alerts to that channel; Dovkie automatically marks the connector as disconnected when Slack tells us the app has been uninstalled.
- Is the bot token stored securely?
- Yes. Bot tokens are encrypted at rest with AES-256-GCM before being written to our database, decrypted only at the moment of sending, and never logged. If your workspace revokes the token, every connector pointing at it is automatically marked as disconnected.
Ready to put Dovkie in Slack?
It's one click to install, one to pick a channel, and you're done.