Hey @Gabe!

For starters, I always recommend apps first try to use the subscription status from the RevenueCat SDK to manage entitlement access which saves you from having to worry about any of this. That said, there are some valid use-cases that require the subscription status be checked from your server instead of the SDK.

So the first thing I would do is ask yourself if it’s possible to use the subscription status from the SDK instead of your server?

The entitlement in question is a monthly subscription to one of our premium features, and I have to manually make a report of all users who were added / removed from this subscription / entitlement, so we can manually turn on/off this premium feature for them.

The simplest approach here could be to generate a Customer List of all the active, and expired customers. You could run this whenever you need your report.

If you need a little more automation than that, the next tool I would look at our ETL exports. These would get delivered daily and you could write a SQL query to get Active and Expired customers over any time period.

The third approach would be to sync subscription status in real-time with your server, so you could query your database whenever you need to to get active/expired subs. This is the most involved approach, and usually starts with listening to webhook events and updating the expiration_date of each customer as new webhooks come through. Use expiration_date here instead of trying to make “subscription statuses”, you can then derive statuses based off of the expiration date (e.g. Active == expiration > now()).

Thanks for detailed response Ryan. 

Still need to test our implementation but I did more or less exactly as you said in your third approach. 

• We refresh the statues of users as webhooks come in, ensuring its up to date.
• Check if the users entitlement is active or expired (expiration > now()) 
• Check the list of active users who we haven’t manually enabled
• Check the list of expired users who we haven’t manually disabled
• ????
• Profit

I have an outline for a blog post I want to write to get into the nitty gritty of keeping your database in-sync via webhooks, but the high level approach I like to use is:

1. Create a sync function on your server that calls the GET /subscriber endpoint to pull the entitlements + expiration_date for the customer.

2. Any webhook event from RevenueCat, sync()

I like this approach because it simplifies your code from having to handle each webhook payload differently, and makes it easy to add fallbacks and redundancy (e.g. you can go back and re-sync if something ever falls over).

@ryan did you ever write this blog? Thanks!

​@op-gg-makingcoolapps Hi! The blog post did not end up getting written, but Ryan’s recommendation for keeping your database in-sync via listening to webhooks and calling the Get Subscriber endpoint still stands as the best method to do so.