Integration options
Choose how you receive SignalWise alerts.
| Option | How it works | Best for |
|---|---|---|
| Kafka (recommended) | Alerts are pushed to your Kafka topic in near real time. | Push notifications and real-time feeds |
| Cloud connectors | Bridgewise forwards the Kafka stream to AWS SQS, EventBridge, Google Pub/Sub or your own API. | Teams that don't run a Kafka consumer |
| REST API | You pull the latest alerts and reasons on demand, filtered by asset, in a chosen language. | Asset pages, feeds rendered on screen |
| Widgets | Embed a ready-made alert and reasoning component with an iframe. | Fastest time to market, no backend work |
| Engagement platforms | Your CRM or engagement platform reads the feed and sends notifications. | Teams already using such a platform |
You can combine them, for example Kafka for push notifications and a widget on your asset pages.
Kafka or REST API?
| Kafka | REST API | |
|---|---|---|
| Delivery | Push, as soon as the alert is ready | Pull, when you call it |
| Latency | Near real time | Depends on how often you call |
| Personalized alerts | Yes | No |
| Effort | Run a Kafka consumer | Simple HTTP calls |
| Typical use | Notifications | Displaying alerts in your UI |
Which message format?
Most feeds use the nested format described in Alert message. Some older feeds use a flat format. Your account manager tells you which format your topic uses, and the schema registered in the Schema Registry is always the source of truth.