#ratmir-aitov_webhooks
sweet stumpBOT
👋 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/1472939961199362224
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
cursive condor
👋 Yes, this is definitely at least surfaced in the Logs https://dashboard.stripe.com/workbench/logs - You will see a Source field indicating if it was from the dashboard, and the specific user that performed the operation, or you will see an API key field that indicates the request was from the API
amber stirrup
Thanks for the reply. Is there access to these logs via API? Or is it overhead in this case?
cursive condor
There's not unfortunately. If you want to do this in some kind of programmatic way, one thing I can think of would be to have your API approach write some metadata to the subscription just before the subscription is cancelled that identifies that the customer is about to delete it, and then this can be referenced to differentiate between API and dashboard cancelled Subscriptions. I don't think there's any more direct way of doing it though