#obo_api
wise thornBOT
đ 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/1357048890007752936
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
dim atlas
I see the metadata object you can pass in when creating / updating a subscription, but I'm more curious about the source of the event itself if that makes sense (IE, our internal systems, an external integration partner, etc)
signal pendant
Hi, yes. What event are you listening to?
dim atlas
the subscription events
customer.subscription.updated, customer.subscription.created, customer.subscription.deleted
signal pendant
In this case, you can pass the metadata: https://docs.stripe.com/api/subscriptions/create#create_subscription-metadata when you create the subscription or when you update it: https://docs.stripe.com/api/subscriptions/update#update_subscription-metadata
dim atlas
yes, I can see that field, unfortunately I'm looking more to track the event itself, and not the metadata on the subscription object if that makes sense
specifically the source of the event
signal pendant
I do not follow, can you reword what you're looking for please?
dim atlas
Sure. We have a few different places in our system that can update subscriptions. (Front-end, Backend, third party provider). Ideally when one of those places updates something, we can have a "source" attribute on that event (so it can be parsed in the webhook that's sent after it).
I'd like to know where the code was called from to create / update a subscription
signal pendant
You can track that and pass that information in the metadata. In the Dashboard, you can see Source but not on the event data
dim atlas
okay, is there a way to see the source information via an additional api call?