#floki_api
kindred talonBOT
đ 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/1483443240479752232
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
modest steppe
hi there!
by "local listener", do you mean with the Stripe CLI?
if so, you can use --forward-connect-to <url>: https://docs.stripe.com/cli/listen#listen-forward-connect-to
vale totem
correct - currently I have one setup with some events but now I'm starting to integrate stripe connect
as it was recommended, regular account events and connect events should have different destinations - so I'm not sure how I can create multiple ones for local listeners so I can test locally
I click "Setup local listener" in dashboard but that does not generate an additional listener
I'm thinking only one is allowed?
through the regular add destination flow
modest steppe
I'm confused. all the screenshots you shared are from the dashboard, so you are not using the Stripe CLI?
vale totem
I am, but I reckon I need to setup the webhook in the dashboard before configuring the cli - right?
for example, this is my setup for stripe-cli:
stripe-listener: image: stripe/stripe-cli:latest container_name: litispay-stripe-listener depends_on: api: condition: service_started env_file: - ./.env environment: STRIPE_API_KEY: ${STRIPE_SECRET_KEY} STRIPE_DEVICE_NAME: docker-dev command: > listen --forward-to http://api:5001/integrations/webhooks/stripe restart: unless-stopped
it works great, but now I need one that routes to
http://api:5001/integrations/webhooks/stripe-connect
and I reckon I need to setup one in dashboard that will give me a different secret key
modest steppe
I don't think that's needed. can you try just updating the command to use --forward-connect-to <URL>, as shown in the link I sharesd above?
vale totem
hmm let me try
I actually need to go run some errands, but later in the day I'll try that out and report back
appreciate the pointer anyways
modest steppe
we may close this thread due to inactivity, but feel free to open a new one if needed when you are back.
vale totem
sounds good - thanks