#try_webhooks-CLI

1 messages ยท Page 1 of 1 (latest)

ivory shoalBOT
#

๐Ÿ‘‹ 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/1446585021816115422

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

iron bramble
#

stripe listen --forward-to http://localhost:8000

Ready! You are using Stripe API Version [2025-03-31.basil]. Your webhook signing secret is whsec_b2d673424dfa7ceef153dce1229fb0388a98dd022d50491b03f90fece77107b2 (^C to quit)
2025-12-05 12:31:11 --> connect capability.updated [evt_1Sb4iJLxNbR55SpPLNsjfbe0]
2025-12-05 12:31:12 <-- [404] POST http://localhost:8000 [evt_1Sb4iJLxNbR55SpPLNsjfbe0]
2025-12-05 12:31:12 --> connect capability.updated [evt_1Sb4iJLxNbR55SpPS6TQXlWC]
2025-12-05 12:31:12 <-- [404] POST http://localhost:8000 [evt_1Sb4iJLxNbR55SpPS6TQXlWC]
2025-12-05 12:31:13 --> connect account.application.authorized [evt_1Sb4iLLxNbR55SpPxNeiuO2V]
2025-12-05 12:31:13 <-- [404] POST http://localhost:8000 [evt_1Sb4iLLxNbR55SpPxNeiuO2V]
2025-12-05 12:31:47 --> connect account.updated [evt_1Sb4isLxNbR55SpPIGGggwg4]
2025-12-05 12:31:47 <-- [404] POST http://localhost:8000 [evt_1Sb4isLxNbR55SpPIGGggwg4]
2025-12-05 12:31:47 --> connect capability.updated [evt_1Sb4isLxNbR55SpPl5HL4CEB]
2025-12-05 12:31:47 <-- [404] POST http://localhost:8000 [evt_1Sb4isLxNbR55SpPl5HL4CEB]
2025-12-05 12:31:47 --> connect capability.updated [evt_1Sb4isLxNbR55SpPyvJ083iB]
2025-12-05 12:31:47 <-- [404] POST http://localhost:8000 [evt_1Sb4isLxNbR55SpPyvJ083iB]
2025-12-05 12:31:50 --> connect account.updated [evt_1Sb4iuLxNbR55SpPingLOIA7]
2025-12-05 12:31:50 --> connect person.created [evt_1Sb4iuLxNbR55SpPhZxP4h1K]
2025-12-05 12:31:50 <-- [404] POST http://localhost:8000 [evt_1Sb4iuLxNbR55SpPingLOIA7]
2025-12-05 12:31:50 <-- [404] POST http://localhost:8000 [evt_1Sb4iuLxNbR55SpPhZxP4h1K]
2025-12-05 12:32:19 --> connect account.updated [evt_1Sb4jOLxNbR55SpPm5wA2IeZ]
2025-12-05 12:32:19 <-- [404] POST http://localhost:8000 [evt_1Sb4jOLxNbR55SpPm5wA2IeZ

#

Some guy here before, @pure pewter told me that I can use only localhost:8000

#

but it seems like not

sand bloom
#

yes it should be your exact URL

#

try_webhooks-CLI

iron bramble
#

Yeah, I changed it and looks good

#

Yeah.. the problem is that I have 2 destinations with different urls in my endpoin

#

endpoint

#

So I think I need run stripe listen again

#

in other terminal with the forward-to for that endpoint right?

#

Because I have 2 destinations in same API.

#

one destination handle some type events, the other one other events.

sand bloom
#

yep

iron bramble
#

Thanks! @pure pewter it seems that I never configured correctly the stripe login

#

I tried again and works, thanks.

sand bloom
#

amazing, thanks for circling back ๐Ÿ™‚

iron bramble
#

thanks @sand bloom

#

see you!