#tidymince_api

1 messages ¡ Page 1 of 1 (latest)

fast sleetBOT
#

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

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

gaunt pumice
devout tendon
gaunt pumice
#

hmm not sure, I haven't used this new API much yet, let me ask my colleagues

devout tendon
#

Thanks a lot!

#

I'm seeing now that support for events cancellation for a time period is coming, maybe this is the answer

#

And by answer I mean that this is how I can achieve what I need

#

But I also see "You can only cancel events within 24 hours of Stripe receiving them." which might not let me do what I need

maiden bough
#

hi! I'm taking over this thread.

#

But I also see "You can only cancel events within 24 hours of Stripe receiving them." which might not let me do what I need
yes that's a limitation we have

devout tendon
#

Does this mean I need to keep track of all the meter events I create?

maiden bough
#

if you want to be able to cancel some of them, then yes.

devout tendon
#

OK

#

Not sure if you're looking for feedback on the meter event api but here's some, hoping it will be useful:

  • considering we're using the meter API to delegate event accumulation and storage to stripe I think it's missing some feature to allow fixing usage (mistakes/bugs happen)
  • if we need to start tracking usage events on our side, we might aswell do the accumulation ourselves and send the usage data before the invoices are generated
  • even if we're ok with tracking usage events on our side, if the mistake/bug happened more than 24h before we're left with no option to fix the usage data

These can be all taken care of by adding the following to the API:

  • capability to cancel a meter event beyond 24h (within the last 35 days like for creating new meter events would ideal)
  • capability to list meter events for a customer within a set time period
maiden bough
#

thanks a lot for the feedback! I'll make sure to forward it to the relevant team.

devout tendon
#

Hope it's useful!

#

Account ID is acct_1Oj5OOIPsU8bKnjX

maiden bough
#

perfect, thanks!

fast sleetBOT