Skip to main content

Handling Your Own Notifications

This guide explains how to handle your own organization consumer notifications by disabling default notifications and using webhooks for event-based notifications or list APIs for scheduled notifications.

Overview​

By default, Stream sends notifications to your organization consumers (customers) for various events like payment confirmations, invoice updates, and subscription changes. If you want to handle these notifications yourself, you can:

  1. Disable default org_consumer notifications - Contact support to enable the blocking setting
  2. Subscribe to webhook events - For immediate, event-based notifications
  3. Use list APIs - For scheduled notifications (reminders, overdue notices, etc.)

Step 1: Disable Default Org Consumer Notifications​

Important: Before disabling default notifications, you must contact our support team to disable default notifications for your organization. This prevents all default notifications from being sent to your organization consumers.

Once enabled, you can manage notifications through webhooks and list APIs as described below.

Step 2: Subscribe to Webhook Events​

For event-based notifications (immediate actions like payment succeeded, invoice accepted, etc.), subscribe to webhook events.

To create or manage your webhooks, go to Webhook Settings and subscribe to the relevant event types.

For a complete list of available webhook events, payload structure, verification, and delivery details, see the Webhooks Guide.

Step 3: Use List APIs for Scheduled Notifications​

For scheduled notifications (time-based reminders like payment due, overdue, etc.), use list APIs with appropriate filters to query for items that need notifications. For example, use the List Payments API, List Invoices API, or List Subscriptions API.