#nukesforbreakfast_docs

1 messages ยท Page 1 of 1 (latest)

icy thunderBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1400562327111336038

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

molten hazel
#

Hi ๐Ÿ‘‹

Thin events are a very confusing topic and I think the docs are just worded poorly.

#

When the docs state "API v1 endpoints also generate thin events." here, my read is that you can use V1 API endpoints to make changes to your Stripe account that will cause V2 thin events to be generated.

somber zephyr
#

so am I understanding correctly that there are only 3 different kinds of v2 thin events today?

molten hazel
#

I currently subscribe to several v1 events. Am I able to use thin events for those?
Thin events are currently limited to the three we have documented here

For other event types you would still need to use V1 events

somber zephyr
#

ok, so basically there are almost no events being sent as "thin" today.

icy thunderBOT
molten hazel
#

Correct. This is a new pattern for us and is not currently a drop-in replacement for V1 events

somber zephyr
#

gotcha

#

does this also mean if I ever need a v2 event, that I need to set up a separate event destination configured for v2 events?

molten hazel
#

I would spin up one in Test mode to validate whether you only receive the three V2 events we listed or whether you get both V1 and V2 events delivered as "snapshot" and "thin" event types