#shashank_webhooks
waxen sageBOT
đź‘‹ 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/1489127457973080214
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- shashank_api, 1 day ago, 25 messages
clear wind
Do you have an example event ID that was not received? (evt_xxx)
median iron
the problem is I am not even receiving the events from the webhook
for connect and v2 accounts
I do not see anything listed under event deliveries
clear wind
right, could you give me access to view your dashboard?
waxen sageBOT
Hello @median iron, we have sent you a direct message, please check it at https://discord.com/channels/@me/1489128483056648263
- đź”— The message has instructions on how to grant read and write access to your Stripe Dashboard for our Developer Support team, in order to help you more effectively.
clear wind
I just sent you a DM for access
median iron
Hi Teddy just wondering why you need the dashboard access? As developer, won't you have access to all the accounts?
clear wind
Our access to user information is now limited due to Stripe's new consent policy. We’re required to send a consent request to users before we can view their dashboard.
This change is part of Stripe’s increased security measures. The dashboard access I’m requesting is read-only, we aren’t given any higher level of access other than that.
median iron
okay sure can you give me a moment? I do not have access to the dashboard myself. Can you share link to allow our CEO to grant the access?
clear wind
The DM i sent you should provide the link, could you check there?
median iron
okay sure thanks Teddy
sorry for the delay. How long will the thread be open?
I am awaiting response from the CEO
clear wind
No problem at all, we can keep it open, take your time.
median iron
Hi our CEO says that he granted the access. Can you check once?
median iron
Did you find out the issue?
clear wind
HeyS sorry for the wait! i do see the events emitted from the connected account (acct_1TH7GqRieyx7Gpae):
- evt_1TH7KKRieyx7Gpae8nCMwEpA (account.updated), created 2026-03-31 18:47:48 UTC
- evt_1TH7HuRieyx7GpaeQSa1Jtnx(account.updated), created 2026-03-31 18:45:18 UTC
- etc…
But like what you said, the web hook endpoint was only created on: 2026-04-01 11:41:30 UTC time, so the events created before the webhook creation time wont be reflected there
median iron
okay are there any permissions that have not been turned on for the restricted key? If account is created from this point on, will the events be sent? I have to note that the old webhook was configured before setting up the connect account. The one we created yesterday has been created after.
clear wind
If account is created from this point on, will the events be sent?
Yes, the events will be sent to the webhook.
That being said, webhooks are a complicated setup, you should test it out thoroughly in your sandbox account, replicating the setup as per you live Platform account and Connected accounts, and testing iit out from there. We have a CLI tool that allows you to test connect webhooks locally: https://docs.stripe.com/connect/webhooks?accounts-namespace=v2#test-webhooks-locally
To be clear, there is a manual retry button available for events—but only for those events that were previously attempted to be sent and failed. This means users can manually retry sending these failed events, but the retry option does not apply to events that haven't been attempted before. https://docs.stripe.com/webhooks#manual-retries
okay are there any permissions that have not been turned on for the restricted key?
Are you referring to the error from this request here: req_eXcmiRo6AnlrDP
median iron
yes I have tried listing the events for the connected account from my terminal however I could not see them. It said the restricted key does not have the permission to do so.
{
"error": {
"message": "The provided key 'rk_live_*********************************************************************************************WVTRnU' does not have the required permissions for this endpoint on account 'acct_1TH7GqRieyx7Gpae'. Please use a different key to perform this action.",
"request_log_url": "https://dashboard.stripe.com/acct_1PeI6yDXcNQJKrcI/workbench/logs?object=req_eXcmiRo6AnlrDP",
"type": "invalid_request_error"
}
clear wind
Right, the reason why you are getting that is because the permissions given to the key (rklive*WVTRnU) do not give it access to the /events API endpoint for both the Platform account and Connected account. See the screenshot attached
You would have to give it "Read" permissions
median iron
okay thank you Teddy. Appreciate the help. So if I write a reconciliation script to retrieve the account status for accounts that have already been set up. I should be able to find out whether the setup was complete and update the status accordingly right?
clear wind
retrieve the account status for accounts
You should actually be able to check the account status and it's capabilites for V2 Accounts from API endpoints actually: https://docs.stripe.com/api/v2/core/accounts/retrieve
median iron
okay thank you Teddy