Fill out this form to request access and be among the first to use what will become Stripe's new default event stream.
Previously limited to API v2, thin events are now available for API v1 resources. This is a major step forward, allowing you to use a single, modern event architecture to listen to all activity across your entire Stripe integration.
For questions, email: treyn@stripe.com
---------------------------------------------
How thin events work
Instead of sending a full, versioned data payload in every notification, thin events provide a more streamlined and reliable pattern:
Event notification: Stripe sends a minimal, unversioned event notification that tells you what happened (e.g., charge.succeeded) and to which resource.
Fetching additional data: Your system receives this lightweight signal and then makes an API call to fetch the full, up-to-date state of that object or fetch the full event payload that includes the fields that have changed
Key benefits
Simplified version management: All API versioning is handled in your client when you fetch the resource. This eliminates event deserialization errors and the need to manage endpoint-specific API versions.
Eliminate stale data: By fetching the object on-demand, you always get its absolute latest state, preventing errors caused by processing outdated or out-of-order event payloads.
