Skip to content

Add note about event type feature flags backwards compatibility #259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tasn merged 1 commit into from
Jan 5, 2026
Merged

Add note about event type feature flags backwards compatibility #259

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/event-types.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1176,10 +1176,14 @@ curl -X POST "https://api.us.svix.com/api/v1/event-type/user.signup/" \
</CodeTabs>

:::info[Important]
Keep in mind that endpoints with no event type filtering will receive all messages regardless of feature flags. Also, users with knowledge of a feature flag-gated event type can subscribe to that event type regardless of feature flags.
Feature flags only impact event types' visibility in the catalog and the API, not their deliverability.
Keep in mind that endpoints with no event type filtering will receive all messages regardless of feature flags.

Feature flags only impact event types' visibility in the app portal, catalog, and the API; not their deliverability. This means that endpoints with no event type filtering will receive all messages regardless of feature flags.

Additionally, if a user is subscribed to a feature flagged event, they will continue to be able to see it in the app portal regardless of whether the feature flag is enabled for them or not.
:::


## Appendix

### Generating an OpenAPI spec
Expand Down