#sethu_org-event-destination
cobalt grottoBOT
👋 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/1419707761721081927
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
frigid sluice
Hello, is there a specific event (evt_123) that you expected to receive but didn't here?
And if so can you send its ID? That API request is of an account link being created, but there isn't an account link specific event
turbid locust
Hi Pompey,
No, we didn't receive the webhook. so I don't see any event ID.
request body:
{
"account": "acct_1S9QFQ8UodwqmpZh",
"refresh_url": "https://assets.setmore.com/integration/static/serviceforge/stripe-integration-completed.html",
"return_url": "https://assets.setmore.com/integration/static/serviceforge/stripe-integration-completed.html",
"type": "account_onboarding"
}
is the idempotency key going to be helpful for you?
frigid sluice
The request ID from before is better, I can see the account link that got created from there. What event are you expecting here? Are you saying that you completed the onboarding flow and didn't get events? Or are you expecting an event about the account link itself being created? We don't send events for account links being created, so the second case would be expected behavior.
frigid sluice
Is there a specific guide you are following here? Typically after this point, the account owner is redirected to that link and completes the steps there in their browser.
cobalt grottoBOT
turbid locust
ok, after login with that url. the webhook will be triggered,, right?
calm valve
Hello 👋
I'm stepping in as my colleague has to go. What specific webhook event type are you listening for?
To be clear, the account onboarding URL is not intended to log the user in. It is intended to securely allow the account owner to provide necessary information to be onboarded as a Stripe merchant that is connected to your platform
I recommend you review our documentation on Stripe hosted onboarding here
turbid locust
We are lisening to the event "account.updated".
calm valve
On what webhook endpoint?
The account.updated event type has been fired many times for this account
But there are no endpoints that are listening for it
calm valve
It seems that is not correctly configured. Can you please share the ID of the webhook endpoint
It will start we_
That is not the webhook endpoint ID
That is the signing secret
Please provide the ID. It will start with we_
calm valve
Go to the detail page for your webhook endpoint. THe ID will be in the URL and on the page.
You can search using Command + F (or Ctl +F) for we_ and it will be highlighted
calm valve
It may be called the Destination ID. Does that start with we_?
calm valve
That doesn't matter
turbid locust
ok.
is Destination ID will help for you?
turbid locust
turbid locust
ok,
I'm seeing that ID under the destination details.
is this a right place that am looking?
calm valve
Sure, just let me see that ID. This looks like you might be set up for V2 events
calm valve
Can you share the ID?
Thank you
Hmmm... These are much harder to view. I can tell you that this event https://dashboard.stripe.com/events/evt_1S9QHQ8UodwqmpZhyabgTahv, which is the most recent account.update event for acct_1S9QFQ8UodwqmpZh was not sent to this endpoint
I recommend you review our docs on listening to events on Connected Accounts
https://docs.stripe.com/connect/webhooks
turbid locust
since we are using the organisation's webhook. so we disabled this event.
The events should be received at this endPoint.
https://dashboard.stripe.com/org_6SxNPJ9KSQ786JAcm2qOHPk/org/workbench/webhooks/ed_61THj7C8JPpXZZIYP26SxNPJ9KSQ786JAcm2qOHPkDwm
From my knowledge, all our production, brand 1 and brand 2. webhooks should receive the webhook that i shared above.
calm valve
You created acct_1S9QFQ8UodwqmpZh and a Connected Account so you should set up this endpoint as a Connect endpoint
turbid locust
How can i set up this endPoint?
calm valve
Please review our documentation: https://docs.stripe.com/workbench/event-destinations
turbid locust
sure, I'll check on this event-destination docl