#yosuf_webhooks

1 messages ¡ Page 1 of 1 (latest)

iron plazaBOT
#

👋 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/1267980697868697710

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

quick umbra
#

Hi there

#

Just to be clear, your team owns the webhook URL/endpoint you use to receive events?

turbid tree
#

Yes, we own the endpoint. We set up a Webhook in the customer's Stripe account using the API Key they've given us, and include the endpoint we own.

quick umbra
#

If so, you could add a query param to the webhook URL/endpoint so you can distinguish between events

#

For example https://example.com?account_id=acct_123... or some other unique identifier from your end

turbid tree
#

Ah gotcha, so when we're creating the Webhook for them, we'd add the query param to the endpoint we pass to Stripe. And then read the query param for the account id when we recieve the event.

quick umbra
#

Yep!

turbid tree
#

That is pretty neat. Thank you!

#

It's late over here but I will try this at some point in the next couple of days and get back to you.

#

Appreciate the help!