xixa-BillingClock | Stripe Developers | Page 1

vagrant hamlet Jan 31, 2022, 4:00 AM

#

I am afraid we haven't supported differentiating them yet. Just in case could you give an example of those wrap up events?

willow mauve Jan 31, 2022, 4:17 AM

#

The main use case would be to delete all entries created by the test clock in the database when the test is over, but never to delete anything when the same type of events are triggered (e. g. customer.deleted and customer.subscription.deleted)

vagrant hamlet Jan 31, 2022, 4:23 AM

#

I mean, an example event id (evt_xxx) 🙂

#

Totally understand your usage

willow mauve Jan 31, 2022, 6:44 AM

#

Oh, haha sorry

#

evt_1KNRxPDsCuAlUWowcvjChbeL

#

Is the id enough?

sharp moss Jan 31, 2022, 6:51 AM

#

heya, stepping in on behalf of orakaro. i honestly can't think of a way to differentiate them other than tracking them yourself. Sorry that we don't have a better solution here

willow mauve Jan 31, 2022, 6:53 AM

#

That's ok, thanks for your time, both of you 🙂

vagrant hamlet Jan 31, 2022, 6:54 AM

#

It's a reasonable feature request, tho

#

I think... the most ideal way to taking the Subscription Id from your event, then perform a Subscription Retrieve API , finding its test_clock property https://stripe.com/docs/api/subscriptions/object#subscription_object-test_clock

Stripe API reference – The subscription object – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

#

Then cross-reference to the clock you have been created (you'll need to save all the clocks created somehow, like Alex said)

willow mauve Jan 31, 2022, 7:07 AM

#

Yeah, I thought of something like that... thank you again!

#xixa-BillingClock