#thebeard_unexpected
1 messages ยท Page 1 of 1 (latest)
๐ 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/1351590173686632448
๐ 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.
- thebeard_api, 6 days ago, 14 messages
Hi! So yes, that is the first invoice of a Subscription, and its period of billing - the period of billable items besides the price. Since there was no period before the start of the Subscription, the period is zero-length.
That period represents the timeframe for which Usage Based Billing items would have been included in this invoice if there were any.
Does that help?
The Invoice's line_items[]interval contain the dates you're likely looking for, which "created date -> next period date"
oh so that period is just for usage based billing? another follow up question i have that is not related to main question: do you know if a subscription does have usage billing , and we set billing threhold and invoice is finalized before period end. that period_end and period_start would be when invoice was finalized right?
yea, that's probably it
Re your first question, that should be the case, yes. It should represent ( period_start || last_threshold ) to new_threshold if that makes sense.
Aka the time since period start, or since the threshold last tripped in this period.
yes, that makes sense. thanks
Awesome. ๐