#joe-davies_webhooks
oak escarpBOT
đ 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/1220071052118593536
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
granite irisBOT
hearty ether
Hi, I do not know how DataDog integration integration works. However, from the context of the question it sounds like you have two Stripe account and listenting to the event on the same URL. In this case, there is not a way to see the account id on the event data. You would need to append the URL with ?account=acct_123 to differentiate the events on the two separate accounts.
tawdry fable
Thank you. Do you think it would be a reasonable Stripe enhancement to include the account ID in the various webhook payloads?
hearty ether
We do with Connect webhook events. Can you share why appending the URL with the specific account id is an issue so I can pass along your feedback?
tawdry fable
I'm going to try appending the URL with the account ID now. I do believe that it's a better experience to simply include the account ID in the json body that's all.
hearty ether
Got it, thank you for sharing this feedback.
tawdry fable
Thank you very much!
granite irisBOT
hearty ether
Sure!
tawdry fable
Appending the following to the DD webhook works perfectly.
&ddtags=accountid:acct_1JUHYZJaaKBKOW8E