#cm5061_docs
wispy oakBOT
đ 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/1436041245800796352
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
rancid bridge
Hi there
Hmm I thought we reverted that change and only duration: 'repeating' was being deprecated. But let me double check on that.
Ah no never mind yes that was removed (I was thinking of something else sorry). We are working on building a replacement where you will be able to set a service period duration with amount_off which can essentially serve the same use case.
dire marlin
So I could plan to migrate to duration: 'repeating' and some value for duration_in_months for now and then upgrade to this replacement in a TBD API release I suppose?
rancid bridge
Yeah that would work
dire marlin
Mainly I was just worried about needing to use the Invoices API for this with the 1-hour finalization. Seems like a tight SLA where if our webhooks were down or something our users could potentially get hit with automatic charges that were larger than expected, which would be bad for us.
Thanks for the clarification!