Skip to main content
Question

Test store renewals - API returns empty entitlements momentarily in between renewals

  • August 8, 2026
  • 2 replies
  • 35 views

Forum|alt.badge.img

Hi, 
I am integrating RevenueCat in my app and currently testing monthly subscriptions using the Test Store.
I tried using the REST V2 api to get the customer’s active entitlements on my backend server. It gives proper response most of the time but during the process of renewal, for about a minute, I get an empty response for active entitlements.
“items”: []

So let’s say I made a purchase at 10:00AM, here is the series of observations:

First purchase → 10:00AM to about 10:04AM - active entitlements present
At around 10:04AM → Set for renewal → Active entitlements empty
~10:05AM → Renewal → active entitlements present

This repeats until the subscription is cancelled automatically after 5 times.

I am using this endpoint:
https://api.revenuecat.com/v2/projects/{project_id}/customers/{customer_id}/active_entitlements

Is this an expected behaviour? If yes, then, is the REST api a reliable source of active entitlements?

Thanks,
Abhi

2 replies

dmatthews-rc
RevenueCat Staff
Forum|alt.badge.img+1
  • RevenueCat Staff
  • August 10, 2026

Hi Abhi,

Thanks for raising this. The test store transaction do indeed have simplified renewal logic where it waits for after the expiration to create the renewal. For production transactions, the API should absolutely be reliable for checking entitlements.

However, since we certainly want the test transactions to give the most accurate simulation possible, I will check with engineering to see if we can improve this experience.

I’ll let you know when I learn more.

Cheers,
Debbie


Forum|alt.badge.img
  • Author
  • New Member
  • August 11, 2026

Hi Debbie,

Thanks, that makes sense. I was wondering if I had to design a solution to handle this case. No need then, I guess.
So, what I understand is that entitlements won’t be empty in between renewals on Production. I will build according to that.

Thanks again,

Abhi