Skip to main content

Hey,

So I’m trying to implement subscriptions with revenuecat with different types of plans (think Spotify like, where you can invite multiple members into your plan).

But in order to do that, I need to store plans/subscriptions data on my own backend.

To offer a real time experience, I need to sync user data with my backend in these scenarios :
- sync data on app launch
- sync data when app comes back to foreground
- sync data right after a purchase (user subscribe and right after I send an api call to my backend to confirm status with revenuecat REST API & sync data)

- sync data with using webhooks

The problem is, the current rate limit is way too low to do this kind of strategy, as said here :
 


This is really important for my user experience, since I don’t want to make the user wait after successfully subscribing to be able to invite other people into the subscription.

What would you suggest in such scenario ? This is a deal breaker for me since it’s a core feature of my app.

Thanks a lot for your time and your help.

Have a nice day.

Hey ​@louis-0770c6,

I think that you could likely simplify the times that you sync with the API in order to decrease your rate. For example, triggering an API ping only when you receive a webhook should keep your backend up to date with any subscription changes that occur, and you would not need to sync data on app launch or when an app is brought back to foreground, as you have already stored any changes to subscription status that may have occurred in your backend.