#deinonychus_webhooks

1 messages ¡ Page 1 of 1 (latest)

hollow shellBOT
#

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

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

past ridge
charred gyro
#

hello! i think the short answer is no, i don't believe this information is included anywhere in the event body. can you share more about your use case and what you're trying to solve for?

past ridge
#

For example, we trigger customer subscription updates from the API, but also some of our account managers will do these actions directly from the Stripe dashboard, and we listen to the events to update the status in our DB. We'd like to differentiate these because when it's done through the API, we want to skip those events.

charred gyro
#

hmm, yeah i don't think there's anything out of the box that would do this for you. i can try to think of creative options for this though

past ridge
#

it's not in the request headers either right?

charred gyro
#

it is not. still digging around to see if i can think of other options

charred gyro
#

ok, i am pretty confident that there is not a good way to do this via the API

#

i was trying to come up with a neat solution using metadata, but since we're looking at subscriptions which persist over time there wouldn't be a good way to quickly tag the subscription with metadata just for the duration of the API triggered event

#

ultimately i think this should be doable, so i'm going to pass product feedback along to our internal team to see if we can get something like this prioritized for future development