#chris-cli-webhook

1 messages · Page 1 of 1 (latest)

native tree
#

We can't really tell you. Those events come from your own account, you should be able to look them up in your Dashboard and look at what created them

dull quiver
#

what property within the object would give that information away?

in fact, the CLI is off now and another was just created

native tree
#

There's no "property" But those are created by your own code, or your own API keys at least

#

you can load a SetupIntent in the Dashboard, and look at the request logs that created/interacted with it

#

it should give you some information on what library is creating them, from which IP address, etc.

dull quiver
#

I'm sorry but I'm having difficulty figuring out where I can check that. I'm in the Developers tab and I see Overview, API Keys, Webhooks, Events and Logs on the left. Is this the dashboard you're referring to?

native tree
#

I mean that's one section of the Dashboard

#

You can search for most objects in the search box at the top, search for the SetupIntent id, load that view, and look at the Logs associated with that resource to try and pinpoint who is creating setupintents on your account

dull quiver
#

Ok, the entire screen is pretty much empty. No logs, no metadata, no customer. The only thing that gives info is the Usage which is "off-session"

thoroughly confused on what is triggering this

native tree
#

Okay can you share an example id?

dull quiver
#

seti_1L5xhbFM6e0F56a9JPjrmnwj

native tree
#

looking

#

oh yeah waht even

#

(digging further but there's none of my usual logs on my end either)

dull quiver
#

odd

native tree
#

uh-oh looks like it comes from loading the docs

#

This shouldn't be happening, let me check

dull quiver
sweet otter
#

Are you by any chance actually using the acct #'s, secrete's or other such from the samples shown?

dull quiver
#

Talking about the secret and publishable keys? No, shouldnt be. I'm using the values stored in the .env file and I got those from the API keys page in the Developers dashboard.

native tree
#

it really just comes from page load on the API Reference. I flagged internally!

dull quiver
#

Ok, Thank you for your work getting to the bottom of it. I was already dreading trying to find that bug haha

native tree
#

yeah I would just say ignore this and we'll try to improve this in the future