#ridero
dawn ridge
rough condor
yes this is what i used before triggering any event:
stripe listen --forward-to http://localhost:5001/{my-app-name}/europe-west1/webhook
if i use a http script and send a request to this endpoint it works fine, only if i trigger the request over the stripe cli it does not receive anything
neon patio
is the url encoding correct
the %7B = { and %7D = }
is your actual endpoint /{my-app-name}/europe-west1/webhook?
rough condor
yes i replaced our real name with brackets and my app name so in the real url they shod not be there
actually it looks like this:http://localhost:5001/MY-APP-NAME/europe-west1/webhook
rough condor
after triggering an event?
the terminal doesnt really output anything except this:
Setting up fixture for: customer
Running fixture for: customer
Trigger succeeded! Check dashboard for event details.
neon patio
no I mean after you start listening to the events
stripe listen --forward-to
this should still be running btw and you should run the fixture in a separate terminal
rough condor
ah ok so thats maybe were i went wrong
i always quitted and triggered in the same terminal
neon patio
the stripe listen is a process that would create a webhook endpoint and register it on Stripe so it would get the webhook events and then forwards them to your local endpoint
rough condor
alright thanks very much that was the issue!
Maybe that would be helpful to mention in the docs (if its not already in there and i missed it) 🙂