Currently I’m reviewing my access flow with API V2. Right now I am using list subscriptions https://www.revenuecat.com/docs/api-v2#tag/Customer/operation/list-subscriptions to capture current_period_starts_at and current_period_ends_at. I use these currently along with gives_access, and status to determine used monthly usage quotas and access. The process seems to work well and line up with what I’m seeing in the docs.
However, my issue come in when status = in_grace_period. Its unclear to me how I can determine the access period range if grace period is active. I read about grace_period_expires_date being used for this in the docs and older community posts, but this field doesn’t seem to exist in API V2 (only in the docs for v1).
What approach is proper using the V2 API?
Handling Grace Period in API V2
+2
+6Hi! The current_period_ends_at field should update to reflect the grace period’s expiration date.
+2Thanks for the reply,
In production can I also expect that current_period_starts_at will retain its original start? Or will it be updated with the grace periods start?
In Sandbox I’m noticing that the 5 min (month) gets extended to 7 minutes as the first warning of a grace period/billing issue. Then after the billing issue and grace period is detected a brand new 5 minute (7day) grace period is started.
Flow in Sandbox
0m-5m original 1 month
0m-7m 1 month after billing issue
7m-12m grace period
12m-onward hold period
This flow breaks my usage quotas so I’m hoping in prod the current_period_starts_at remains through the grace period.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.