#fakossaconate-webhook-delivery

1 messages · Page 1 of 1 (latest)

stray oxideBOT
#

Hello! We'll be with you shortly. 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.

#

fakossaconate-webhook-delivery

spice inlet
#

Can you share an example event id where this happened?

potent warren
#

yes, thanks

#

evt_1OUtbtIadRGc5clFosjtKIJx

#

a checkout session completed

spice inlet
#

That event wasn't sent to any webhook endpoint

#

The only webhook endpoint you have registered is a connect endpoint

#

That is a platform event though

#

But even if it was a connect event it wouldn't have been delivered

#

Because your endpoint isn't set up to listen for checkout session completed events

potent warren
#

Tjis is not how to set t up?

#

dev page, webhook. I follow the instruciton (here in the screenshot). No mention of a connect endpoint here

spice inlet
#

It's when you create the endpoint

#

You can't edit it after the fact to listen to platform events

#

When creating you need to select this:

#

You selected events on connected accounts

#

Also you're clearly not listening to checkout.session.completed events anyway

#

Which is the example event type you sent me

potent warren
#

yes I had deleted it to keep success and failure after all but I think I got it. Thank you for your response. Have a nice day

spice inlet
#

Same to you