#Bero
1 messages ยท Page 1 of 1 (latest)
HI ๐
We don't know a whole lot about Reports here. This server is focused on unblocking developers coding integratiosn with Stripe APIs.
If you are referring to the Report Run API, you can pass interval_start and interval_end parameters to define the data that will be included in the report.
I'm doing integration of Stripe Checkout and using Subscriptions. and when u are doing subscription you have to report usage. Here is docs: https://stripe.com/docs/products-prices/pricing-models#reporting-usage
Ah, okay. So there a strict timeframes in which you can update usage in the past. Let met check on these
Yes we explain we have a very small grace period to account for server clock drift. We mention it here: https://stripe.com/docs/products-prices/pricing-models#reporting-usage
yes i want to know if this grace period is configurable? or how many minutes are configured now?
So you may be able to submit your usage records at 00:01 on Sept 1st
what about at 01:00 on Sept 1st?
We do not publish a set grace period and we explicitly tell you not to rely on this for your reporting
okay in that case when i want to push usage record for whole month
from 1 August 00:00
to 31 August 23:59
on what time should I run my cron job in my backend server and what timestamp should i use when i am pushing usage record to Stripe Backend?
I would recommend you use the timestamp of 31 August 23:59 and your job should run 1 Sept 00:00
okay so basically u are saying that if my job will take more than lets say 5 minute, it might fail or might be successful because of grace period no?
so i should make sure that job is finished within 2 minutes maximum so that grace period problem is solved.
I would test it out to verify the behavior you expect but I would think a 4 minute span would be sufficient
Thank you very much ๐