Skip to main content
Question

How to replicate the “Entitlements” overview card from the dashboard in my own admin panel?


Forum|alt.badge.img

Hey team,

I'm trying to build an admin view similar to the "Entitlements" card shown in the RevenueCat dashboard (see attached screenshot), but I'm struggling to figure out how to get this same level of detail through the API.

Screenshot

 

Here's what I’ve tried so far:

  • API v1 (Get Customer):
    This gives me a list of all entitlements a user has ever had, but:

    • There’s no connection to their subscriptions. (I cannot find out the different grant periods as in screenshot).

    • It doesn’t tell me if a subscription will renew.
      (On the dashboard, I see “Will renew in X” — but there’s no equivalent field here.)

  • API v2 (Subscriptions endpoint):

    • I can list the subscriptions and join it with product data to infer durations, renewal status, etc.

    • But promotional entitlements break this:

      • Subscriptions created by granting entitlements don’t have product IDs.

      • The entitlements field in the subscription only includes active entitlements.

      • So if a promotional entitlement expired, the subscription ends up with no product and no entitlement.

  • Purchases endpoint:
    Doesn’t provide enough detail to rebuild the full entitlement/subscription history (for instance, for promotional entitlements, there is no purchases associated to the user).

I know I could store event data on my side and build the full picture myself — but I don’t have capacity to set that up right now.

Is there a recommended way to get the same view of a customer’s entitlement/subscription history that’s shown in the dashboard?
Or a better endpoint I might be missing?

Thanks!

 

 

 

4 replies

wes_clark
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 284 replies
  • April 17, 2025

Hi, There is not an endpoint that will get you this exact information. Your best option may be to merge these two approaches in order to identify the entitlements that have been granted by app store purchases and those that have been granted. Although I see that you mention wanting to not store the event data on your end, I did want to highlight the Scheduled Data Exports tool as this would allow you to query this data more easily.


Forum|alt.badge.img+2
  • Member
  • 5 replies
  • April 18, 2025

Why isn’t there a single endpoint that can do this? If you have the data to be able to show it in the admin section why is it so hard to make it accessible via an API endpoint?


Forum|alt.badge.img
Brighttank wrote:

Why isn’t there a single endpoint that can do this? If you have the data to be able to show it in the admin section why is it so hard to make it accessible via an API endpoint?

Totally with you on this.
My latest half‑baked idea is to spin up a second “bot” RC account, invite it to the project, and just hit the normal dashboard APIs from there so I can rebuild the exact entitlements view.
Same deal with the Metrics API: the UI shows growth curves, but the endpoint only hands back raw totals.


Forum|alt.badge.img
wes_clark wrote:

Hi, There is not an endpoint that will get you this exact information. Your best option may be to merge these two approaches in order to identify the entitlements that have been granted by app store purchases and those that have been granted. Although I see that you mention wanting to not store the event data on your end, I did want to highlight the Scheduled Data Exports tool as this would allow you to query this data more easily.

 

Thanks for the quick answer, Wes.

RevenueCat already removes a lot of pain around in‑app purchases, so first off—kudos. One request from the developer side: the dashboard shows a unified entitlement history, but pulling that same view requires 4–6 separate calls on our end. A single read‑only endpoint (or an extension of the Metrics API) would lower our call volume and your server load—a win for both sides.

The same point applies to the Metrics API: the UI shows trends and growth, yet the public endpoint only returns the base values.

I get why these endpoints aren’t public—RC’s core job is the purchase plumbing, and you already provide webhooks and scheduled exports for deeper analysis. But for something like the Entitlements overview, having a direct API feels like it fits squarely in that mission.

Appreciate the tip on Scheduled Data Exports. I’m on a tight timeline right now, so I’ll circle back to that (and the webhooks) when things calm down.

Thanks again!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings