#simon_webhook-live

1 messages ยท Page 1 of 1 (latest)

green owlBOT
#

๐Ÿ‘‹ 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/1479170471873216654

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

autumn sleet
#

๐Ÿ‘‹ I'm happy to help but I'm going to need a bit more details. Can you share an example Event id evt_123 that you think should have been sent but wasn't?

#

simon_webhook-live

manic hill
#

Hi ๐Ÿ™‚
Now we are only receiving v2.* events.

#

evt_65UGYLsVGfWJbCmVBZX16TKxIwATGRvYpJZ8g4IMGzACt6

autumn sleet
#

Sorry is that the id of an Event you recieved or didn't receive?

#

v2 Events are completely separate from v1 Events and require a different kind of WebhookEndpoint configuration

manic hill
#

our webhook is only listening for v1 events, which are not arriving.

#

for example:

autumn sleet
#

Can you please give me an exact Event id that you think you should be receiving but you are not though? That's what I need to debug

manic hill
#

I don't have any v1 event in tab "events"

autumn sleet
#

๐Ÿ˜“

manic hill
#

I'm sorry, I have just registered an express account via API and no one v1 event fire. Why?

autumn sleet
#

there's no account.created Event, so Events would happen once you do things on that connected account

#

Sorry trying to help but not finding the right words.

You're a Connect platform. You have connected accounts. You can view all those connected accounts in your Dashboard and all their logs and Events too in their own dashboard view. That lets you more easily debug things

#

Give me the id of that connected account and I can have a look though!

manic hill
#

just a second please

#

acct_1T7fo4GkQtS6FbkO

autumn sleet
#

Okauy so we do send Events and your endpoint returns with an error in Italian about the signature being incorrect

#

maybe you forgot to change the WebhookEndpoint's secret?

#

What I recommend is adding logs to your webhook handler so you can narrow it down and debug this further

manic hill
#

yes we are Italian, I've update webhook with correct signature now but now I have this error:

Received event with API version 2026-02-25.clover, but Stripe.net 48.5.0 expects API version 2025-08-27.basil. We recommend that you create a WebhookEndpoint with this API version. Otherwise, you can disable this exception by passing throwOnApiVersionMismatch: false to Stripe.EventUtility.ParseEvent or Stripe.EventUtility.ConstructEvent, but be wary that objects may be incorrectly deserialized.

We developed entire integration with *basil version. Webhook as well is set with that version

autumn sleet
#

hum

#

Can you log the exact Event id first?

#

The one I looked at was sent with Basil

manic hill
#

sure:
evt_1T7fo7GkQtS6FbkOXekL4j4V

autumn sleet
#

yeah this one is not normal. Can you create a brand new connected account again and share that new account id so I can have a look?

green owlBOT
manic hill
#

Yes, can you wait an hour?

autumn sleet
#

We'll keep this open for a bit, but otherwise just ask a new question

manic hill
#

Ok, thank you

autumn sleet
#

Okay sorry I figured it out. We have a really old bug where Event account.application.authorized and account.application.deauthorized are sent with the wrong API version.
Sadly it's a really hard one to fix and we haven't been able to.

#

So I think your integration is likely working, just this Event specifically has the wrong version and you have to handle it (or ignore that Event)

manic hill
#

Ok, now we are creating a brand new account

sly topaz
#

FYI i'm taking over for koopajah, let me know if you have any more questions beyond what they said in their most recent messages

manic hill
#

ok, now we are receiving v1 events correctly

sly topaz
#

can you share an example event ID? what all did you change to make it work correctly?

manic hill
#

after webhook destination recreation and setting correct webhook signature

#

evt_1T7fqfGkQtS6FbkOunPTcxRU

sly topaz
#

ok great! as koopajah mentioned above there is a known bug where account.application.authorized and account.application.deauthorized events specifically are sent using your account's API version rather than the webhook version, so if you need to handle those events you should be prepared to handle that