API Connect

API Connect

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

Introducing Slack, PagerDuty, and Email Destinations in the API Connect v10.0.10 Engagement

By Dipan Mukherjee posted 12 days ago

  

In today’s fast-moving digital landscape, timely communication is key to effective API management and operations. That’s why in IBM API Connect v10.0.10, we’re expanding the capabilities of Engagement — our built-in alerting and notification system — by introducing new, easy-to-configure destination types.

What’s New?

Previously, API Connect allowed you to configure webhook destinations — enabling notifications to be sent to any HTTPS endpoint. With v10.0.10, we are taking this a step further by adding direct integrations with:

  • Slack – For real-time team collaboration and visibility into API activity.

  • PagerDuty – For operational alerting and incident management.

  • Email – To ensure reliable communication across your teams, even when other systems are down.

These destinations can be configured at both the organization and catalog levels, giving you flexibility to tailor notifications based on your operational needs.

Why This Matters

With these enhancements, API Connect now allows you to:

  • Alert the right teams faster using tools they already work in (like Slack or PagerDuty).

  • Ensure important events are never missed, even during downtime, with reliable email notifications.

  • Customize engagement per environment, so production alerts can go to different recipients than test or development alerts.

 How It Works

From the API Connect UI or API, you can now select destinations across four types:

  • Webhook. Send a message to any HTTPS endpoint you specify.

  • Slack  Post real-time messages directly to your Slack workspace         

  • PagerDuty  Trigger incidents and alerts in your PagerDuty service

  • Email Send notification emails to specified recipients.

All destination types are managed consistently through the Engagement interface, so you can control where and how your notifications are sent — no custom scripting required.

Looking Ahead

These new destination types open the door for deeper integration into your SRE and support workflows. Whether you're coordinating with teams in Slack, monitoring incidents in PagerDuty, or falling back on reliable email — API Connect makes it easier to stay informed and act.

0 comments
22 views

Permalink