backend

Automate RevenueCat backend operations for Android subscription management via REST API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps backend developers efficiently manage RevenueCat state on Android, eliminating the need for a receipt verification server and providing a clear workflow for interacting with the RevenueCat REST API.

Core Features & Use Cases

  • REST API Interaction: Offers direct access to the RevenueCat REST API for subscriber management, entitlement granting, and attribute setting.
  • Secret vs Public SDK API Key Usage: Clearly differentiates between public and secret API keys for secure and controlled access.
  • Backend Workflow Automation: Automates common backend tasks like subscription state updates, entitlement changes, and attribute updates.
  • Use Case: Imagine you need to automate the process of granting promotional access to users or setting attributes in RevenueCat. This Skill provides the necessary commands and guidance to accomplish these tasks efficiently.

Quick Start

Set up backend operations with RevenueCat by configuring the REST API endpoints and implementing the webhook receiver.

Frequently Asked Questions about backend

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

FAQPage Schema
How do I manage RevenueCat subscriptions without building a custom receipt verification server?

You can manage RevenueCat subscriptions without a receipt verification server by using the RevenueCat REST API to directly handle purchase events, validate subscriptions, and update user attributes from your backend.

How do I automate granting promotional entitlements to Android users via the RevenueCat REST API?

Automate granting entitlements via the RevenueCat REST API by calling the backend endpoints to update subscriber state, manage entitlements, and set user attributes for Android applications.

Do I need a secret API key or public SDK API key for backend operations with RevenueCat?

Backend operations with RevenueCat require a secret API key for secure server-side access, whereas the public SDK API key is used for client-side integration to ensure controlled access.

Can I use this backend approach to handle Android purchase events and validate subscriptions through RevenueCat?

Yes, this backend approach handles Android purchase events and validates subscriptions by interacting directly with the RevenueCat REST API, automating workflow updates without a custom verification server.

What is the best way to configure a webhook receiver for RevenueCat backend operations?

The best way to configure a webhook receiver for RevenueCat backend operations is by setting up the REST API endpoints to listen for subscription state updates and entitlement changes.

Are there limitations to managing RevenueCat state directly through the REST API instead of a custom server?

Managing RevenueCat state through the REST API eliminates custom server maintenance but requires correctly differentiating secret and public API keys to ensure secure access and prevent unauthorized entitlement updates.