Skip to main content
Question

Checking entitlements via API after receiving a webhook

  • April 23, 2026
  • 2 replies
  • 36 views

Forum|alt.badge.img

Hi,

we are implementing the recommended flow for syncing subscription information on our backend with RevenueCat, as described here: https://www.revenuecat.com/docs/integrations/webhooks#syncing-subscription-status.

Each time we receive a webhook, we call the RevenueCat API to fetch the current information about the user’s entitlements. Based on that response, we determine whether the user should have premium access.

We are using the v2 Get Customer endpoint. After receiving a webhook, we call this endpoint and check the active_entitlements field in the response.

I have a question regarding consistency:

Does RevenueCat guarantee that, after receiving a webhook, calling the API will always return up-to-date entitlement information?

For example, if we receive an expiration webhook and then immediately call the API, is it guaranteed that the active_entitlements field will already be empty because the user’s subscription has expired and the entitlements have been removed?

Thank you for your help.
Jan Zabloudil

2 replies

Forum|alt.badge.img
  • Author
  • New Member
  • April 23, 2026

A better approach is probably to check expires_at for each entitlement in active_entitlements. However, the question still remains the same:
when I receive, for example, a RENEWAL event and call the endpoint, is it guaranteed that I receive entitlements with an updated expires_at?


wes_clark
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • April 29, 2026

Hi ​@jan-zabloudil! Yes, RevenueCat can guarantee that the v2 Get Customer Endpoint will provide the most up-to-date customer data after you have received the webhook.