#clayton_api

1 messages ¡ Page 1 of 1 (latest)

copper ploverBOT
#

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

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

true hazel
#

Hi, let me help you with this.

#

Could you please share the example Subscription Schedule ID?

fathom owl
#

Yes, here is an exampl I created and then update to start on the 17th and then updated again to start on the 16th.
sub_sched_1QWmNZS3LSlk1l2CAP5MXNmR

#

This invoice structure also creates problems for monthly coupons that normally shouldn't get applied to the first partial month. Here they get applied and then the discounted price is part of the calculation that goes into crediting the next month.

true hazel
#

Have you tried setting the billing_cycle_anchor to the 1st of the month? In this case, you might not even need to use Subscription Schedules (unless you want to start the Subscription in the future)

#

But looking at your Subscription Schedule configuration, this Invoice configuration is expected.

fathom owl
#

When I create an active subscription it works perfectly to set the billing_cycle_anchor to the 1st. The use case is to have a Subscription start automatically in, for example, 10 days from now. 1st invoice is for Dec 27-Jan 1, second invoice is for Jan 1-Feb 1.

true hazel
#

For that you can create a Schedule with just one phase, but also with start_date in the future. No need for 2 phases.

fathom owl
#

So what would the start date be set to? Dec 27th? and how would I make sure it knows the billing cycle should be the 1st of every month. There is no parameter to specfcy that for Sub Schedules, only 'phase_start' or 'automatic'.

true hazel
#

I just tried it and it seems like it's not possible to set start date to an arbitrary date with Subscription Schedules, unfortunately.

#

Unfortunately, if you want to start the Subscription at later date with SubSchedules, the Invoices will behaved the way you obseved initially.

#

I can only suggest trying to use Subscription with trial_end to start it on a date in the future, instead of Subnscription Schedules.

fathom owl
#

Hmmm ok. So essentially the Subscription is active but with free trial days until the desired start date.

#

That is complex but could work.

true hazel
#

In any case Subscription Schedules are usually more complex to manage.

copper ploverBOT
fathom owl
#

Ok, if I had one suggestion it would be to expose that "Billing Cycle Starting" field as a parameter in the Sub Schedule API similar to how it is present in the UI, and present on the Subscription API, highly customizable to specific days of the month instead of just 'phase_start' or 'automatic'

#

When I am able to set that to 1st, it works as I would expect.

true hazel
#

Makes sense. I guess since Subscription Schedules already is a complex API, it was decided to keep at least some options limited initially.