Rate limiting for identity currently_entitled_tiers?

Hey I’m currently using this route

to get the user’s current tier and verify that they have access to certain content.

I wanted to ask if there are any drawbacks to this and if I could potentially get rate limited for making these calls whenever a user requests to see a post.

My other idea was to get it once on login and store it and then use the webhooks to update my database.

What would be the best solution for this?


Making the call whenever user sees a post is not a good idea. Implementing a very short term cache for the api result, populating it when a user views a post, and then using it for a very short duration of time would be better.

A combination of calls to identity/ (when users actively login to your app), webhooks and a cron that syncs your campaign is a good idea to keep your stuff in sync.