kevinx9999-_webhooks

[twin fossil]

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.

• kevin_connect-webhooks, 40 minutes ago, 118 messages

[warm kayak]

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1249875567826960404

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

[potent shadow]

Hello there

We have three different webhooks and two different checkout pages (for different line_items)

I'm just trying to figure out how the events from different checkout pages are sent to these webhooks

I have read the docs and haven't found the clear answer yet

[knotty gazelle]

Hi there, so you want to know more about the checkout.session.completed event?

[potent shadow]

not only this event, but all other events that we are listening to from different webhooks, some are overlap, some are not
I'm just trying to figure out how the events from different checkout pages are sent to these webhooks

[knotty gazelle]

Do you have some examples?

[potent shadow]

ok, here are three webhooks we have

when a checkout page sends an event like account.updated or charges.successeed, how is this event being sent to the webhook, which webhook?

[knotty gazelle]

Ok so you are talking about webhook endpoints.

It really depends on the endpoint configuration (i.e., what event is the endpoint is listening to)

For example the endpoint https://www.zykles.com/api/listingWebhook is only listening to charge.succeeded. charge.dispute.created and charge.dispute.updated

[potent shadow]

https://www.zkyles.com/api/connectWebhookOwners , this endpoint listens to the same events

[knotty gazelle]

https://www.zkyles.com/api/connectWebhook is listening to checkout.session.completed, but the event delivery wasn't successful. Example: https://dashboard.stripe.com/events/evt_1PPnSpF9VtVx6MBBWDADYHVJ

[potent shadow]

ok, why?

[potent shadow]

actually all three endpoints are listending to some same events with the same event names

that's where my question comes in, how Stripe sends events to different endpoints

[knotty gazelle]

You can open the link that I sent earlier to go to your Dashboard and see why the event wasn't delivered successfully

[potent shadow]

It says Failed to connect to remote host

[knotty gazelle]

https://www.zkyles.com/api/connectWebhookOwners is a connect webhook endpoint and it will only listen to events from your connected accounts. Are you using Connect?

[potent shadow]

yes, I am

ok, I should ask this way,

[knotty gazelle]

OK. And I can see that both of your account webhook endpoints (https://www.zykles.com/api/listingWebhook and https://www.zkyles.com/api/connectWebhook) are listening to some commoen events, i.e., charge.succeeded event, which means they will both get notified when a charge.succeeded happens.

However, I noticed that you reused https://www.zkyles.com/api/connectWebhook to listen to events from your account and also connected accounts, this is not something I'd recommend.

[potent shadow]

what do you mean reused here

is there any config that points a checkout session to a webhook endpoint?

[knotty gazelle]

Ah sorry, my mistake, they are using two different URLs.

"points a checkout session to a webhook endpoint?' -> can you elaborate more?

[potent shadow]

ok, let's say I have two different checkout pages for two different line_items

and I want to have webhook endpoint A listen to checkout session A only

and webhook endpoint B listens to checkout session B only

[knotty gazelle]

Not possible

[potent shadow]

and why it is failed to connect to the remote host

[knotty gazelle]

You might want to check with your hosting provider and make sure your endpoint is always accessible.

[potent shadow]

ok, so if an event is generated, it just blasts to all webhook endpoints? of course, seperate between accout and connect

[knotty gazelle]

Yes you are right

[potent shadow]

ok, to further confirm, if all of my endpoints listen to charge.successeed, once this event is generated from ANY checkout pages, all three endpoints will receive the event?

[knotty gazelle]

If the charge.successeed is genereated from your account,
https://www.zykles.com/api/listingWebhook and https://www.zkyles.com/api/connectWebhook will be notified.

If the charge.successeed is genereated from one of your connected account, https://www.zkyles.com/api/connectWebhookOwners will be notified.

[potent shadow]

great
I actually set up the listingWebhook and connectWebhook for two different items, as there are two different group of actions following up

if the same event are sent to both webhooks, how should I config to determine which items was sold

[knotty gazelle]

You can listen to checkout.session.completed event, and expand (https://docs.stripe.com/api/expanding_objects) the checkout session object to get its line_items

https://docs.stripe.com/payments/checkout/fulfill-orders#fulfill you can find an example here

[potent shadow]

ok, so if this is the case, I don't actually need two endpoints at all for ACCOUNT

since all the same events are delivered everywhere indiscriminately

just one endpoint for account and another for connect, is this the right approach?

[potent shadow]

I know why it is failed, because my host has a rate limit to prevent DDOS I guess, if Stripe blasts the same events mutiple times in a short time to different webhook endpoints, the second would fail

Hello, you there?

[knotty gazelle]

What's the question?

[potent shadow]

ok, so if this is the case, I don't actually need two endpoints at all for ACCOUNT
since all the same events are delivered everywhere indiscriminately
just one endpoint for account and another for connect, is this the right approach?

[knotty gazelle]

Yes, it looks good to me.

[potent shadow]

ok, thanks

is it a good practice, if we use different webhook endpoints listen different events for the same account?

[knotty gazelle]

It's not required, but you can do it if some events are happening too frequent and you need to setup a dedicated endpoint to take the load.

[potent shadow]

oh, I see, thanks

Have a good day there!