#matih_webhooks

1 messages · Page 1 of 1 (latest)

vestal beaconBOT
#

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

📝 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.

glad mulch
#

👋 happy to help

vestal beaconBOT
strange mason
#

This is what happens:

$ stripe events resend evt_1RqYiMAZXatHl2PMpM6IkSgG
{
  "error": {
    "code": "resource_missing",
    "doc_url": "https://stripe.com/docs/error-codes/resource-missing",
    "message": "No such notification: 'evt_1RqYiMAZXatHl2PMpM6IkSgG'",
    "param": "id",
    "type": "invalid_request_error"
  }
}
grim dock
#

Hello
are you sure you're logged into the correct account on the CLI?

strange mason
#

yes, im sure. how can i verify?

grim dock
#

Resource missing errors usually point to Object not existing/belonging to the account you've logged into

#

you can try running stripe login again

strange mason
#

this is what's printed in the console:

> Ready! You are using Stripe API Version [2025-06-30.basil]. Your webhook signing secret is whsec_bed35715923ca744fc883a230380dcf7d1d89dabc423fb87e04c87a616d0a6e3 (^C to quit)
2025-07-30 14:02:33   --> connect account.updated [evt_1RqYiIAZXatHl2PM1Sfmhxfq]
2025-07-30 14:02:34  <--  [500] POST http://127.0.0.1:80/dashboard/webhooks/direct/ [evt_1RqYiIAZXatHl2PM1Sfmhxfq]
2025-07-30 14:02:35   --> connect account.updated [evt_1RqYiKAZXatHl2PMMaPF8ILV]
2025-07-30 14:02:35  <--  [500] POST http://127.0.0.1:80/dashboard/webhooks/direct/ [evt_1RqYiKAZXatHl2PMMaPF8ILV]
2025-07-30 14:02:35   --> connect account.updated [evt_1RqYiKAZXatHl2PMLJU1KnQF]
2025-07-30 14:02:35  <--  [500] POST http://127.0.0.1:80/dashboard/webhooks/direct/ [evt_1RqYiKAZXatHl2PMLJU1KnQF]
2025-07-30 14:02:36   --> connect account.updated [evt_1RqYiLAZXatHl2PMVQ6j2GxE]
2025-07-30 14:02:36  <--  [500] POST http://127.0.0.1:80/dashboard/webhooks/direct/ [evt_1RqYiLAZXatHl2PMVQ6j2GxE]
2025-07-30 14:02:36   --> connect person.created [evt_1RqYiLAZXatHl2PM7mbuwH81]
2025-07-30 14:02:36  <--  [500] POST http://127.0.0.1:80/dashboard/webhooks/direct/ [evt_1RqYiLAZXatHl2PM7mbuwH81]
2025-07-30 14:02:37   --> connect account.updated [evt_1RqYiMAZXatHl2PMpM6IkSgG]
2025-07-30 14:02:37  <--  [500] POST http://127.0.0.1:80/dashboard/webhooks/direct/ [evt_1RqYiMAZXatHl2PMpM6IkSgG]
2025-07-30 14:02:38   --> connect account.updated [evt_1RqYiNAZXatHl2PM3u28CVYZ]
2025-07-30 14:02:38  <--  [500] POST http://127.0.0.1:80/dashboard/webhooks/direct/ [evt_1RqYiNAZXatHl2PM3u28CVYZ]
#

using the first evt_id (in the same console):

$ stripe events resend evt_1RqYiIAZXatHl2PM1Sfmhxfq
{
  "error": {
    "code": "resource_missing",
    "doc_url": "https://stripe.com/docs/error-codes/resource-missing",
    "message": "No such notification: 'evt_1RqYiIAZXatHl2PM1Sfmhxfq'",
    "param": "id",
    "type": "invalid_request_error"
  }
}
grim dock
#

Nice, so you see the "connect" string before the event type? That suggests that this is an event that's related to Stripe Connect

strange mason
#

Yes, as it should be. Don't understand what you're implying though?

grim dock
#

That event belongs to your connected account - acct_1RqBXKAZXatHl2PM
You are likely logged into to your Platform account on the CLI

#

So you need to specify --account while resending

strange mason
#

hmm, but this is the platform which allows companies to sign up (as Connected Accounts). shouldn't the Webhook event belong to the platform?

grim dock
#

Depending on the type of events, it may belong to Platform or the Connected Account.
Using connect type webhook, you'd be able to listen to and receive events from your Connected Accounts - https://docs.stripe.com/connect/webhooks

Receiving the webhook events does not imply ownership

#

Connect webhooks
A Connect platform uses two types of webhooks:

  • Account webhooks are for activity on your own account (for example, most requests made using your API keys and without authenticating as another Stripe account). This includes all types of charges, except those made directly on a connected account.
  • Connect webhooks are for activity on any connected account. We send all events on the connected account (including account updates and direct charges) to the Connect webhooks.
strange mason
#

We send all events on the connected account (including account updates and direct charges) to the Connect webhooks

Well, this explains it! Thank you!

grim dock
#

NP! 🙂