#braydensterrett

1 messages ยท Page 1 of 1 (latest)

royal swanBOT
sleek python
#

Hi ๐Ÿ‘‹

Do you have events in your Dashboard that are firing but not being deliverd?

clever parrot
sleek python
#

Or is the event not firing?

clever parrot
#

No, no events ever show up

#

I am able to receive them on a localhost if I configure that.. but never on a live endpoint

sleek python
#

Do you have an example event ID I can check?

clever parrot
#

Well, I have one from the localhost.. is that what you want?

#

"evt_1Nq1APRcwNtMVUt5VzkG7GIc"

#

I would expect this to fire on both the configured localhost listener and the configured webhook endpoints.. but I'm only seeing the listener working

#

Since we've deployed this to a production-like staging environment, we need to validate against a live webhook endpoint instead of the local listener at this point.

#

I've also verified that the endpoint that I've configured does, indeed, exist on the server and is public facing

#

It's weird to me that we're not even seeing the events show up as trying to be delivered by Stripe

#

I'm also positive that the "account.updated" events should be firing. I'm able to see the Stripe::Account get created in our Stripe dashboard and see the account updates happen as I go through the onboarding forms

sleek python
#

Okay the Webhook endpoint you shared was created today

clever parrot
#

Yeah I just created it about 20 minutes agoish

sleek python
#
created    2023-09-14 20:48:55
clever parrot
#

Eh, maybe more like 50 mins lol

sleek python
#

So can you try using the CLI with stripe trigger account.updated to see if that gets to your registered endpoint?

clever parrot
#

I'm not really able to run that on this server since it's in a production environment.. I have been able to make this work on my localhost though

#

The events don't show up in the Stripe webhook UI though, they show up in my terminal on the listener

sleek python
#

If you run stripe trigger account.updated it will fire the event in test mode. But that will hit your registered webhook endpoints

#

Can you provide an account.updated event that occurred after you created the endpoint?

clever parrot
#

Just ran that, but no events are showing up

sleek python
#

When you say "no events are showing up" what are you referring to?

clever parrot
#

I'm expecting some events to show up here, no?

#

Here's an event ID for one that is showing up.. but it's not an event type that I care about: "evt_1NqNIeDdMtGGqypumj6rx5P6"

#

For instance, here's another app that I have webhooks configured on an endpoint. This page is full of events

#

Perhaps I have the endpoint configured improperly ๐Ÿค”

#

I just added another endpoint with the "Events on connected accounts" option checked.. maybe that's what I want?

sleek python
#

I don't look at the endpoint specifically, I look at all the events.

#

The account the webhook is on is acct_1NNhn3DdMtGGqypu. Is that the account where these events are happening?

#

It will receive account.updated events for that Account.

clever parrot
#

acct_1NqN00RV3roDNcKp is the one I've created

sleek python
#

If you want to get events for updates that occur on Connected Accounts you need a Connect endpoint

clever parrot
#

Okay, maybe I just configured it correctly. Let me try to send a webhook and see what happens

#

We don't want updates to our account, we want them on our user's created connect accounts

#

Ahhh that was definitely it! Sorry for the run around. I just wasn't quite understanding the difference between the two endpoint types. I think it makes sense now.

#

Seeing events flowing

sleek python
#

No worries! Yeah the account.updated event fires on each account. So you can only get those events forwarded to your platform account by setting up a Connect webhook endpoint

clever parrot
#

Got it, got it. Thanks a bunch for the help!