Discover the benefits of Stripe's new public preview release channel, designed to provide early access to cutting-edge API features before their general availability. Start innovating faster with Stripe’s latest offerings while sharing your feedback to shape future developments!
Overview
Stripe has launched a new public preview release channel that allows developers to access upcoming API features before they are generally available. This initiative aims to enhance innovation by enabling early integration and feedback on new functionalities.
What You'll Learn
1
How to access new Stripe features using the public preview release channel
2
Why using distinct API versions for public preview features is beneficial
3
When to expect breaking changes in public preview API versions
Key Questions Answered
What is the purpose of Stripe's public preview release channel?
The public preview release channel allows developers to access new API features before they are generally available, enabling early integration and feedback. This channel is designed for operationally stable features that may still undergo breaking changes.
How do you make API calls to the public preview features?
To access public preview features, developers must send a preview API version via the Stripe-Version header, such as '2025-04-30.preview'. This ensures that the request targets the correct version of the API that includes the new features.
What are the key differences between GA and public preview API versions?
Public preview API versions are distinct from GA versions, allowing for more frequent changes and breaking changes based on user feedback. GA versions are more stable and have fewer breaking changes, typically occurring twice a year.
What restrictions may apply to public preview features?
Public preview features may have geographic restrictions, require onboarding or approval from Stripe, and are subject to more frequent breaking changes. Each feature's documentation outlines specific restrictions.
Technologies & Tools
Backend
Stripe API
Used to access and integrate new features through the public preview release channel.
Key Actionable Insights
1Utilize the public preview release channel to experiment with new features early.By accessing features before they reach GA, developers can build and test integrations sooner, providing valuable feedback to Stripe that can influence final implementations.
2Be aware of the potential for breaking changes in public preview API versions.Since public preview versions may change more frequently, it's crucial to monitor the changelog for updates and adjust integrations accordingly to avoid disruptions.
3Leverage the distinct API versioning to manage feature rollouts effectively.Using separate versions for public preview allows teams to integrate new features while maintaining stability in existing GA functionalities, reducing risk during deployment.
Common Pitfalls
1
Assuming public preview features are fully stable and production-ready without checking documentation.
While public preview features are operationally stable, they may still undergo breaking changes and have restrictions that could affect integration, so it's essential to review the documentation thoroughly.
Related Concepts
API Versioning
Feature Rollout Strategies
Feedback Loops In Software Development