How to Set Up Slack Alerts for API Monitoring

Your API goes down at 2 AM. The first person to notice is a customer who tweets about it. By the time you wake up, there are 30 support tickets and a Hacker News thread about your outage.

This is what happens when you don't have alerts where your team actually looks. And for most engineering teams, that place is Slack.

In this tutorial, you'll learn how to set up Slack alerts for API monitoring with Nurbak — so you get notified about downtime, latency spikes, error rates, and SSL expiry in the channel where you already work.

Why Slack Is the Best Channel for API Alerts

Engineers don't check email at 2 AM. They don't keep a monitoring dashboard open 24/7. But they do have Slack on their phone with notifications enabled for specific channels.

Slack is where your team already communicates about incidents. When an API alert lands in #ops-alerts, the on-call engineer sees it immediately, and the rest of the team has full context without asking "what happened?"

Compared to other alert channels:

• Email — gets buried, delayed by spam filters, often ignored outside work hours
• SMS — limited formatting, no context, annoying for non-critical alerts
• PagerDuty/Opsgenie — great for escalation, but overkill for most teams under 20 engineers
• Slack — instant delivery, rich formatting, threaded discussion, mobile push notifications, and it's already open

That's why Nurbak sends Slack alerts using Block Kit — Slack's rich message format — so you get structured, actionable notifications instead of plain-text noise.

How Nurbak Sends Slack Alerts

When Nurbak detects an issue with one of your monitored API endpoints, it sends a formatted message to your Slack channel via an incoming webhook. The message uses Slack's Block Kit format, which means you get a structured notification that includes:

• Endpoint name and URL — e.g., Payment API — POST /api/v1/checkout
• Current status — Down, Degraded, or Recovered
• Monitoring region — which region detected the issue (Virginia, São Paulo, Paris, or Tokyo)
• Response time — the actual response time vs. your configured threshold
• HTTP status code — the status code returned (e.g., 503 Service Unavailable)
• Timestamp — when the incident was detected
• Direct link — a button that takes you straight to the incident in the Nurbak dashboard

This is not a generic "something is wrong" email. It's a structured alert with everything you need to start investigating immediately.

Step 1: Create a Slack Incoming Webhook

First, you need a webhook URL from Slack. This is the endpoint Nurbak will POST alert messages to.

1. Go to api.slack.com/apps and click Create New App
2. Select From scratch, name it something like "Nurbak Alerts", and choose your workspace
3. In the left sidebar, click Incoming Webhooks and toggle it On
4. Click Add New Webhook to Workspace
5. Select the channel where you want alerts (e.g., #ops-alerts or #api-monitoring)
6. Click Allow — Slack will generate a webhook URL

Copy the webhook URL. It will look like this:

https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX

Keep this URL private. Anyone with it can post messages to your Slack channel.

Step 2: Add the Webhook to Nurbak

Now connect that webhook to your Nurbak account:

1. Log in to watch.nurbak.com and go to Settings → Alert Contacts
2. Click Add Contact and select Slack as the channel type
3. Paste your webhook URL
4. Give it a label (e.g., "Engineering Alerts" or "#ops-alerts")
5. Click Send Test Notification to verify — you should see a test message appear in your Slack channel within seconds
6. Click Save

That's it. Nurbak can now send alerts to your Slack workspace.

Step 3: Configure Alert Rules

Having Slack connected is only half the setup. You also need to define when Nurbak should alert you. Go to your project's Alert Rules page and configure these rules:

For each rule, select your Slack contact as the notification channel. You can also add email as a backup — Slack might be down too (it happens).

What the Slack Notifications Look Like

When an alert fires, you'll see a Block Kit formatted message in your Slack channel that looks like this:

    🔴 API Down — Payment API
Endpoint: POST /v1/checkout
Status: 503 Service Unavailable
Region: Virginia (US)
Response Time: 12,450ms (timeout)
Detected: 2026-03-25 02:14 UTC
[View Incident →]

The message is color-coded: red for down, yellow for degraded, and green for recovery. The "View Incident" button links directly to the incident timeline in your Nurbak dashboard, where you can see the full check history, response headers, and latency breakdown (DNS, TLS, TTFB).

When the endpoint recovers, you get a follow-up notification:

    ✅ Recovered — Payment API
Endpoint: POST /v1/checkout
Status: 200 OK
Region: Virginia (US)
Response Time: 187ms
Downtime: 8 minutes
Recovered: 2026-03-25 02:22 UTC
[View Incident →]

Anti-Spam: One Notification per Incident

Nobody wants their Slack channel flooded with repeated alerts every 60 seconds. Nurbak follows a one notification per incident model:

• 1 alert when the incident starts (after the configured threshold is crossed)
• 1 recovery notification when the endpoint is healthy again
• No repeated alerts during an ongoing incident

This means if your API is down for 30 minutes, you get exactly 2 Slack messages — not 30. Your #ops-alerts channel stays clean and every message in it is worth reading.

If you need more granular updates during an incident, the Nurbak dashboard shows the full timeline with every individual check result.

Pro Tip: Create a Dedicated Alert Channel

Don't send API alerts to #general or #engineering. Create a dedicated channel like #api-alerts and configure it so:

• Only monitoring tools post to it (Nurbak, your CI/CD, etc.)
• On-call engineers have mobile notifications enabled for this channel
• Everyone else can check it when they need context on an incident

This keeps your main channels clean while ensuring alerts never get lost in conversation noise.

Get Started

Slack alerts are available on the Pro plan ($29/month), which also includes 1-minute health checks, multi-region monitoring from 4 regions, and unlimited alert contacts. The free plan includes email alerts for up to 3 endpoints.

Start monitoring your APIs with Nurbak — setup takes under 3 minutes, and your first Slack alert can be live before you finish your coffee.