#jefskoa_webhooks

1 messages ¡ Page 1 of 1 (latest)

vocal fernBOT
#

👋 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/1407705721188909099

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

grim adder
#

hi there!

#

I'm not sure I understand your question. can you give more details?

coral lion
#

Sure! I have a .net webhook app receiving webhook post from Stripe developer account. I need to get the connected account for the triggered webhook, but not finding it. I suspect the "stripe trigger <event>" command does not, by default use the test connected account in the HTTP header as I can't find it. I"m wondering if there's a way to inject it when I trigger a stripe event for testing the webhook app. Hope that helps ...

grim adder
coral lion
#

Thx, I also notice in the JSON body, there's an "account" element that is null. Is that null ONLY because it is a dev account? Will that also contain the connected stripe account in a production account?

grim adder
#

if it's an event that came from a connected account, there should be an account ID in the response.

#

can you share the Event ID (evt_xxx) where it's missing?

coral lion
#

evt_1RyBNWIvHz5DOm3ovVurvt7J

#

Thanks for helping me! This is cool stuff.

grim adder
#

this event happened on account acct_1Qpv01IvHz5DOm3o, and was sent to acct_1Qpv01IvHz5DOm3o. so this has nothing to do with connect.

#

looks like you didn't create a webhook endpoint on the platform to listen to events on the connected accounts?

coral lion
#

On my PC, I am using the Stripe CLI. I did a successful "Stripe Logon" and then used:
stripe listen --events reporting.report_run.succeeded,payout.updated --forward-to localhost:64492/v1/webhooks/receive/stripe
to forward events to my .net app. This part is working. I am receiving the web hook. I have the Stripe-Signature in hand. Just missing the connected account. I just tried the --stripe-account option as you suggested from the command line:

stripe trigger payout.updated --stripe-account acct_1Qpv01IvHz5DOm3o

but still do not see that in the header, nor the "account" element. Am I missing something in the way I'm doing the trigger?

vocal fernBOT
south badge
#

Hi there, taking over for @soma as they need to step away, going to investigate this now

coral lion
#

Thx! Let me know what I can clarify/provide.

south badge
#

Can you verify which account you logged into for your Stripe CLI? You can verify this by running stripe customers create and then send me the customer ID you get from the response

coral lion
#

C:\Users\jsutherl\source\StripeCLI>stripe customers create
{
"id": "cus_Su00rSFh26agOr",

south badge
#

Looking at this customer, it was created on your connected account. This means you are logged into your connected account at the moment, which is the cause of your current issue.

You need to be logged into the platform first, then you can use the stripe listen command with --forward-connect-to <url> in order to receive the event that has the account ID that you are looking for
https://docs.stripe.com/cli/listen#listen-forward-connect-to

If you do this, then you will see the account attribute from the Event that you are expecting. You can see in the docs that this attribute only exists when you are using Connect
https://docs.stripe.com/api/events/object?api-version=2025-07-30.preview&rds=1#event_object-account

coral lion
#

When you write "logged into the platform first" you mean via the Stripe CLI, not on the Server/Dashboard side?

south badge
#

Yes, Stripe CLI must be logged into with your platform account

coral lion
#

Is there something different in the stripe login then to login at the platform level first? I didn't see the option when I viewed the stripe cli docs.

#

It appears from the stripe cli docs, when I do Stripe Login, it logs me into the platform (???). Then if I want a specific account I have to specify that on the command to trigger the event, ie: stripe trigger payout.paid --stripe-account acct_123456.

slow meteor
#

Hey @coral lion -- just giving @south badge a hand here. You'd select the account context in the Dashboard flow triggered by the CLI during login

#

The CLI should redirect you to the Dashboard to confirm the CLI session login, at which point you'd be able to pick an account where you have Dashboard access to multiple.

#

If you have separate Dashboard accounts, you'd need ot make sure you're logging into the one with platform access

#

We can see from the customer that got created that the CLI is definitely using the connected account currently

#

So you should stripe logout then stripe login again, and check for an account switcher

coral lion
#

doing that now. not seeing the account switcher. could it be because I'm logged into the account in another tab so I can issue commands?

slow meteor
#

If you're looking at the Dashboard, do you have access to switch to the platform account in the top left?

#

If not, it sounds like you might need to log in to a different Dashboard account for platform access, which would be needed for logging the CLI in using the platform

coral lion
#

No, the Dashboard indicates I'm logged into a Connected account. Switch accounts is not active. Does that mean my profile/login is only connected to the sandbox connected account, not the platform?

slow meteor
#

Correct

#

You need Dashboard access to the platform to use the CLI as the platform

coral lion
#

I will pursue that access.

#

That should only apply to our Sandbox platform and connected account under that sandbox platform, correct?

vocal fernBOT
fiery python
#

Hi taking over here. give me a bit to catch up

fiery python