webhooks

Process RevenueCat webhook events for subscription state transitions.

45|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/RevenueCat/play-billing-skills --skill webhooks-revenuecat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhooks
Source: https://github.com/RevenueCat/play-billing-skills/tree/main/revenuecat/webhooks
Command: npx skills add https://github.com/RevenueCat/play-billing-skills --skill webhooks-revenuecat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you integrate and handle RevenueCat webhooks on your backend, ensuring you can process normalized event schema and manage various subscription states.

Core Features & Use Cases

  • Event Handling: Process events such as INITIAL_PURCHASE, RENEWAL, CANCELLATION, and more.
  • Idempotency Management: Handle idempotency via the event id field to avoid duplicate processing.
  • Access Management: Manage subscription access changes like CANCELLATION, EXPIRATION, and RENEWAL.
  • Use Case: Automate backend logic for managing user subscriptions and entitlements based on RevenueCat webhook events.

Quick Start

Use the webhooks skill to set up your webhook endpoint and process events from RevenueCat.

Frequently Asked Questions about webhooks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle RevenueCat webhooks for subscription management on my backend?

To handle RevenueCat webhooks, set up a webhook endpoint to receive normalized JSON event schemas and process subscription state transitions like INITIAL_PURCHASE, RENEWAL, and CANCELLALITY. This automates backend logic for managing user entitlements.

How does idempotency work when processing RevenueCat webhook events?

Idempotency in webhook processing is managed via the event id field, ensuring duplicate event deliveries do not trigger duplicate state transitions. This prevents redundant backend operations and maintains accurate subscription access.

What subscription event types can I process with RevenueCat webhooks?

You can process various subscription event types including INITIAL_PURCHASE, RENEWAL, CANCELLATION, and EXPIRATION. Handling these normalized events allows you to manage backend subscription state transitions and user access changes automatically.

How do I manage user entitlements when a subscription cancellation webhook is received?

When a CANCELLATION or EXPIRATION webhook is received, you use the normalized event schema to trigger backend access management logic. This updates the user's subscription state and revokes their associated entitlements.

What is the best way to automate backend logic for RevenueCat subscription state transitions?

The best way to automate subscription state transitions is to consume RevenueCat webhooks and process the normalized JSON event schema. This approach handles idempotency and automatically updates entitlements for events like renewals and cancellations.