#alalva_api
outer stumpBOT
đ 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/1268230679024369664
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
ripe steppeBOT
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.
- alalva_api, 23 hours ago, 7 messages
- alalva_api, 1 day ago, 6 messages
- alalva_alalva-customer-portal-configuration, 4 days ago, 17 messages
blazing star
By default both of those calls will prorate based on your current time. Our prorations are pretty granular, so if the user makes the change even minutes later it would be expected for the price to differ a bit
To get these to line up, you can save the timestamp that we use for proration on the original invoice and pass that as the proration_date in the actual update call when you make it
Or you can pass a timestamp to both calls. For example you could pass UTC midnight of the day that the call is being made
solemn light
ok let me try to save the timestamp and use it in the invoice as the proration date. Thank you