#jemen_docs

1 messages ยท Page 1 of 1 (latest)

pine quarryBOT
#

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

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

runic basalt
#

hi there, give me awhile to check

timber root
#

Yeah, of course. I've just find out this.

You don't need to configure any webhook endpoints in your Dashboard to receive webhooks with the CLI.

#

But I don't understand how is this possible.

#

So by default I'm getting all those events.

#

And by flags I'm using I just filter them, right?

runic basalt
#

Can you share with me an event that failed? Also it is possible to receive webhook events with CLI without configuring endpoint in your Dashboard.
When you do stripe listen --forward-to localhost:4242/public/webhook.php it should give you a webhook secret

timber root
#

Yeah, I might use stripe listen, so I can listen without setting up destination address on dashboard.

runic basalt
#

Could you copy and paste the event ID for me please (evt_xxxxxx)

timber root
#

evt_1Rsh6OFAPdZ3ImfzLCnT1Bqf

runic basalt
timber root
#

The URL is publicly accessible on the internet

#

This is not possible

#

But it should not be problem when using stripe listen, right?

runic basalt
#

yup

timber root
#

Great, thanks! ๐Ÿ™‚