← Back
Stripe
Stripe updates event destinations `events_from` parameter to support string values, adds organization filtering
Stripe APIStripe · apibreaking-change · docs.stripe.com ↗

Parameter Update: Enum to String Conversion

The events_from parameter on the EventDestination object has changed from a nullable array of enums to a nullable array of strings. This change affects how you configure event routing in Stripe webhooks and event destinations.

New String Values

The parameter now supports four string values with namespace-style prefixes:

  • @self – Events from the account that owns the destination (replaces self)
  • @accounts – Events from connected accounts of your platform account (replaces other_accounts)
  • @organization_members – Events from accounts in your organization (NEW)
  • @organization_members/@accounts – Events from connected accounts of platform accounts in your organization (NEW)

Breaking Change Details

SDK type definitions that previously used typed enum unions (self | other_accounts) must now accept string types. The API will automatically convert legacy enum values you provide as input (for backward compatibility), but responses will return the new string format. For example, if you set self as input, it will be converted to @self in API responses.

Required Action Items

  1. Update any code that checks for specific events_from values to expect the new string format instead of the enum values
  2. Upgrade SDKs for all supported languages (Python, Java, Node.js, Go, PHP) to the latest version
  3. Update your API version to 2026-03-25.dahlia in Workbench
  4. Test your integration thoroughly, including Connect integrations if applicable
  5. Update webhook endpoint API version configurations

The old enum values are accepted on input for backward compatibility, but you should migrate your code to use the new string values to avoid future issues.