Move V2.Event API resources to V2.Core.Events#3200
Merged
xavdid-stripe merged 3 commits intomasterfrom Sep 29, 2025
Merged
Conversation
…ventDestination and V2.EventNotification to V2.Core, and UnknownEventNotification to Stripe.Events
xavdid-stripe
requested review from
helenye-stripe and
jar-stripe
and removed request for
a team
helenye-stripe
approved these changes
Sep 29, 2025
This was referenced Oct 2, 2025
This was referenced Oct 23, 2025
This was referenced Oct 30, 2025
This was referenced Nov 13, 2025
This was referenced Nov 20, 2025
This was referenced Dec 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
In
2024-09-30.acacia(docs), we released our new V2 Event system, found under the/v2/core/eventsAPI endpoint. When we put them in our in SDKs, for presentation reasons, we put these new resources in theStripe.V2.Eventnamespace.We've realized that dropping
Corefrom the SDK namespace adds more confusion than good, so we're putting the v2Eventresource into theStripe.V2.Corenamespace, where you'd expect to find it in the first place.There's no change to specific event classes, like
V1BillingMeterErrorReportTriggeredEvent. Those are, and will continue to be, underStripe.Events.What?
V2.EventstoV2.Core.EventsChangelog
Event,EventDestination,EventReasonetc) fromStripe.V2toStripe.V2.Core. They now correctly match their API path and are in line with all other resources. To update your code:Stripe.V2.Event->Stripe.V2.Core.EventStripe.V2.EventDestination->Stripe.V2.Core.EventDestinationStripe.V2.EventReason->Stripe.V2.Core.EventReasonStripe.V2.EventReasonRequest->Stripe.V2.Core.EventReasonRequestStripe.V2.EventRelatedObject->Stripe.V2.Core.EventRelatedObjectStripe.Events.V1BillingMeterErrorReportTriggeredEvent) haven't moved.