# Rate limiting for identity currently\_entitled\_tiers?

**URL:** <https://www.patreondevelopers.com/t/rate-limiting-for-identity-currently-entitled-tiers/7421>\
**Category:** Friendly Help\
**Created:** [May 2, 2023, 7:25pm UTC](https://www.patreondevelopers.com/t/rate-limiting-for-identity-currently-entitled-tiers/7421 "2023-05-02T19:25:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![emersonh-xyz](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/emersonh-xyz/32/2300_2.png) [@emersonh-xyz](https://www.patreondevelopers.com/u/emersonh-xyz)\
**Post date:** [May 2, 2023, 7:25pm UTC](https://www.patreondevelopers.com/t/rate-limiting-for-identity-currently-entitled-tiers/7421/1 "2023-05-02T19:25:37Z")

</div>

Hey I’m currently using this route  
[https://www.patreon.com/api/oauth2/v2/identity?include=memberships.currently\_entitled\_tiers](https://www.patreon.com/api/oauth2/v2/identity?include=memberships.currently_entitled_tiers)

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?

Thanks!

---

<div class="post-metadata">

**Author:** ![codebard](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/codebard/32/14_2.png) [@codebard](https://www.patreondevelopers.com/u/codebard)\
**Post date:** [December 6, 2023, 10:19am UTC](https://www.patreondevelopers.com/t/rate-limiting-for-identity-currently-entitled-tiers/7421/2 "2023-12-06T10:19:24Z")

</div>

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.