revenuecat-api-quick-reference

To configure the RevenueCat Android SDK, use the `Purchases.configure()` builder options to initialize the SDK with your specific API key and establish the necessary purchase handling context.

The RevenueCat REST API requires specific authentication headers and JSON payloads to manage users. Use the reference to identify the correct paths, authentication methods, and payload structures for user management operations.

To handle Android billing errors with RevenueCat SDK 10.x, reference the common usage patterns and error resolution guidelines to ensure API usage best practices and avoid pitfalls related to the SDK surface.

Yes, the RevenueCat REST API is suitable for backend integrations and server logic. It provides paths, authentication methods, and payload structures needed to manage purchases and users without requiring the mobile SDK.

If your RevenueCat purchase handling returns an unexpected type, check the SDK 10.x reference for the correct API call return types and builder options to ensure proper usage patterns and avoid common SDK pitfalls.