Handle RevenueCat events without cutting access early.
Guides backend webhook implementation so subscription events update user access correctly without applying duplicate deliveries.
When to use it
Use when consuming RevenueCat webhooks on a backend.
It changes how the agent implements RevenueCat webhook handlers, requiring signature checks, deduplication, and event-specific dispatch.
What you provide
Requires a server-side HTTPS endpoint that accepts POST requests with a JSON body.
Requires durable storage for processed event IDs and entitlement state per app user.
Requires the webhook secret obtained from the RevenueCat dashboard under Integrations then Webhooks; how the handler loads it is unstated.
No additional actions listed.