#julson_webhooks
thorny tendonBOT
👋 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/1328811758109851739
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
warped mist
Hi, I can confirm that the event was sent with the updated API version: https://dashboard.stripe.com/test/events/evt_3QhFtZCQkFi8IKk80FxuqP1o. You can also confirm it in the Dashboard from this link and look at "api_version": "2024-12-18.acacia",.
quaint solstice
oh! strange. Is it a workbench thing?
I did check our records and it looks like it was in the right version (includes the latest_charge field)
but this dashboard shows otherwise
warped mist
When you say 'Dashboard' where are you exactly looking?
quaint solstice
warped mist
Is that not the API version of the request, https://dashboard.stripe.com/test/logs/req_ohk7ntaZXGxwEs since it's below the Source?
Yeah, that is the version of the request and not the webhook event. I was able to confirm this on my own test account
thorny tendonBOT
warped mist
You can see the API version of the webhook under 'Destination details' on the webhooks tab
quaint solstice
I thought it would show me the webhook event itself. What's confusing me is that the event data shows it sending the "charges" object, while the one in our records shows "latest_charge"
Here's what we have in our DB
So it does seem like it's behaving properly under the hood, but the dashboard doesn't match it
dapper cloud
Hello
Taking over as my colleague needs to step away soon
Give me a second to catch up
quaint solstice
all good. Thank you @warped mist
dapper cloud
Your webhook endpoint API version is set correctly to 2024-12-18.acacia. Your account's API version is set to 2020-08-27
When something happens on Stripe - We generate two events in this case. One for the account's default API version and the other for the webhook endpoint API version.
As far as I know, the dashboard shows the object generated for account's default API version. The event that you receive on your endpoint would be in the format of 2024-12-18.acacia version.
quaint solstice
I see. that makes sense. I'm only seeing the default version of the event then
but once we upgrade then it should line up
dapper cloud
Yup, give me one moment as I thought we also showed the exact payload that was delivered. Maybe in the event details view?
dapper cloud
Ah check here - https://dashboard.stripe.com/test/events/evt_3QhFtZCQkFi8IKk80FxuqP1o
Under webhook attempts
hmm not sure if you can open the link above with workbench 🤔
quaint solstice
yeah that's why i'm wondering if it's a workbench thing
because I do remember seeing the correct version when testing in the past. I just switched to workbench recently
dapper cloud
Can you look under webhooks and share a screenshot of the UI?
If you select your event destination > event deliveries > search for event ID --- I believe you should be seeing the correct payload
with latest_charge
dapper cloud
Yeah that's definitely wrong.. That's not the payload we'd have sent. I believe its a workbench rendering bug. According to logs on our end, we definitely sent the event with latest_charge parameter
quaint solstice
yeah. also confirmed it from our backend
thorny tendonBOT
Hello @quaint solstice, we have sent you a direct message, please check it at https://discord.com/channels/@me/1328824941319159929
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.