New behaviour for Webhook events subscription

Starting today, when you create or update a Webhook subscription, you can only subscribe to events that currently exist and not to events that may be added in the future.

Impact on new Webhook subscriptions

• In the application, the option “Trigger on all events (current and future)” is removed.
• In the API, the subscribed_eventsparameter of Webhook management endpoints still accepts the * value, but it now only covers the events that exist at the time of the creation or update. It will not include future events.

Impact on existing Webhook subscriptions

Existing Webhook subscriptions with subscribed_events set to * will continue to work, but they will only receive events that exist as of today.

Behavior when a new event is added to the API

When new Webhook events are added in the future, existing subscriptions with subscribed_events set to * will not receive them automatically. To receive newly added events, you will need to update your Webhook subscription to include them explicitly.

Why this change?

• When new events are introduced, automatically pushing them to all wildcard (*)-enabled Webhooks can generate noise, unexpected traffic, and unwanted side effects in your systems. By requiring explicit event selection, we ensure you only receive events you have chosen to handle.
• A more sober and intentional handling of events reduces unnecessary processing, simplifies troubleshooting while keeping the overall Webhook system efficient.

If you have any questions about this change, please contact our support team, we're here to help.