#Foxted-connect

1 messages ยท Page 1 of 1 (latest)

half yoke
#

Hello! Give me a few minutes and I'd be happy to help

half yoke
#

Quick question - is the webhook your checking an account webhook or a connect one?

jade bloom
#

A connect one

#

Using the Stripe CLI during development, it was working fine, but now on staging it seems like that webhook doesn't get triggered ๐Ÿค”

half yoke
#

Is it that the webhook is not receiving the event at all, but you see that it exists, or that no account.update event exists at all?

jade bloom
#

I can't see any account.update event being triggered

#

I checked the live account as well just in case, but nothing

half yoke
#

Do you have an account ID I can take a look at?

jade bloom
#

The connect account ID or our platform account ID?

half yoke
#

The connect account ID

jade bloom
#

acct_1K1ELZRKTO3KDTIr

half yoke
#

Are you still testing this out with the CLI? What's the stripe listen command you're using?

jade bloom
#

Yes I checked the CLI to see if the event was triggered (and it was when using stripe listen)

half yoke
#

Did you have any additional flags to the stripe listen command?

jade bloom
#

No flags

half yoke
#

You mentioned earlier that you had it working during development but now it's not working on staging - what specifically are you doing differently between development and staging?

jade bloom
#

During development, I was testing the webhook using stripe listen --forward-to

#

In the documentation somewhere, it is mentioned that connect test webhooks could sometimes be sent via the live account, but when looking at the production webhook, I don't see any event triggered either

half yoke
#

Why did you remove the --forward-to flag for your current testing?

jade bloom
#

Because I was testing on our staging environment (which has the API deployed), I only use the forward-to when pointing to my API running locally (in development)

half yoke
#

I think I'm starting to see what the disconnect is - let me know if my understanding of your current state is correct:

  • You were testing things out earlier with stripe listen --forward-to and everything was working fine
  • You stopped running the stripe listen command because now you want to test your staging environment that has been deployed
  • You're not seeing anything come into those staging webhook endpoints
#

Is that correct?

jade bloom
#

That's correct

half yoke
#

One last question - how did you register the staging endpoint as a webhook endpoint? Did you do it through the dashboard? I'm asking becuase I don't see any connect webhooks for the platform account right now (which would explain why none are being sent to your endpoint)

jade bloom
#

I did it for the dashboard, but I just realized: maybe our current endpoint only works for the platform account ๐Ÿ˜ฑ

#

I might have to create a second one for connect indeed!

#

The endpoint is the same for both on our end, would you recommend two separate endpoints?

half yoke
#

It's really up to you - personally, I'd have them be two separate endpoints since I assume they serve very different purposes in your integration

jade bloom
#

Fair enough, I'll update our API then ๐Ÿ™‚ I just tried it and I can see the event being triggered now, thanks for your help! ๐Ÿค˜๐Ÿป