Stripe | Financial Infrastructure to Grow Your Revenue

Stripe | Financial Infrastructure to Grow Your Revenue

4466 articles

Updates the events_from parameter on event destinations to accept string values


Breaking changes

Updates the events_from parameter on event destinations to accept string values Breaking changes

What’s new

Updates the events_from parameter on the EventDestination object to be a nullable array of strings instead of a nullable array of enums. It accepts the following strings:

  • @self : events from the account that owns the destination (replaces the self enum value)
  • @accounts : events from connected accounts of your platform account (replaces the other _ accounts enum value)
  • @organization _ members : events from accounts in your organization
  • @organization _ members/@accounts : events from connected accounts of platform accounts in your organization

Why is this a breaking change?

The events_from parameter changes from an enum type to a string type and uses different values. SDK type definitions that previously used a typed enum union ( self | other_accounts) must now use string. If your integration expects the previous values, you need to update your code to expect the new values.

Impact

You can now set the events_from parameter to one of 4 string values when creating event destinations instead of using the previous 2 enum values. Update any code that checks for specific events_from values in API responses to expect the new values.

The API continues to accept the previous values as input, so you don’t have to update your code for creating destinations. However, Stripe automatically converts the enum values to the corresponding string values. For example, if you set the value to self, it becomes @self. You need to update any code that expects it to be self.

Changes

FieldsChangeFrom → to
V2. Core. EventDestination#create. events_from V2. Core. EventDestination. events_fromChangedenum('other_accounts'|'self') → string

Upgrade

  1. View your current API version in Workbench.
  2. If you use an SDK, upgrade to the corresponding SDK version for this API version.
  • If you don’t use an SDK, update your API requests to include Stripe-Version: 2026-03-25. dahlia
  1. Upgrade the API version used for webhook endpoints .
  2. Test your integration against the new version.
  3. If you use Connect, test your Connect integration .
  4. In Workbench, perform the upgrade . You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Last verified 2026-09-24

Is this helpful?