SouffleAuChocola

[wary garnet]

there is not a foolproof way, no.

generally the approach is that you add metadata when creating an object from your own code and you can check if that exists

[heavy moon]

would be really helpful if there were a way to identify that without a metadata.

We have this sensible situation with a client who is claiming they've used our API for creating the subscription thus resulting in a issue which cannot be reproduced in our development environment. But if they used the Stripe dashboard instead , this could be the reason.

[wary garnet]

makes sense. It's a common question for years but the answer is mostly the same

[heavy moon]

so the best approach would be marking these events with metadata if API is used.

[wary garnet]

for completeness I'll mention that https://stripe.com/docs/api/events/object?lang=node#event_object-request exists if an event was triggered by an API request, but it's not foolproof since the Dashboard can also call the API and fill that field

[heavy moon]

Thank you ! We'll definetly consider implementing this to avoid these kind of situations.