Package-level declarations
Types
Specifies behavior for a caching API.
Class containing all information regarding the customer
Only use a Dangerous Setting if suggested by RevenueCat support team.
This object gives you access to all of the information about the status of a user's entitlements.
This class contains all the entitlements associated to the user.
Verification strictness levels for EntitlementInfo.
This annotation marks the experimental preview of the RevenueCat Purchases API. This API is in a preview state and has a very high chance of being changed in the future.
Interface that allows handling logs manually. See also Purchases.logHandler
Enum of supported ownership types for an entitlement.
Contains information about the product available for the user to purchase. For more info see https://docs.revenuecat.com/docs/entitlements
Enumeration of all possible Package types.
Enum of supported period types for an entitlement.
Contains information about the proration mode to use in case of a product upgrade. Use the platform specific subclasses in each implementation.
The result of a successful purchase operation. Used in coroutines.
Entry point for Purchases. It should be instantiated as soon as your app has a unique user id for your user. This can be when a user logs in if you have accounts or on launch if you can generate a random user identifier. Make sure you follow the quickstart guide to setup your RevenueCat account.
This class represents an error
The result of the verification process.
Functions
Get latest available customer info. Coroutine friendly version of Purchases.getCustomerInfo.
Gets the StoreProduct(s) for the given list of product ids of type type, or for all types if no type is specified.
This function will change the current appUserID. Typically this would be used after a log out to identify a new user without calling configure
Logs out the Purchases client clearing the save appUserID. This will generate a random user id and save it in the cache.
Fetch the configured offerings for this users. Offerings allows you to configure your in-app products via RevenueCat and greatly simplifies management. See the guide for more info.
Initiate a purchase with the given PurchaseParams. Initialized with an Activity either a Package, StoreProduct, or SubscriptionOption.
Restores purchases made with the current Play Store account for the current user. This method will post all purchases associated with the current Play Store account to RevenueCat and become associated with the current appUserID
. If the receipt token is being used by an existing user, the current appUserID
will be aliased together with the appUserID
of the existing user. Going forward, either appUserID
will be able to reference the same user.
This method will send all the purchases to the RevenueCat backend. Call this when using your own implementation for subscriptions anytime a sync is needed, such as when migrating existing users to RevenueCat.
Get latest available customer info.
Get customer info from cache or network depending on fetch policy.
Fetch the configured offerings for this users. Offerings allows you to configure your in-app products vis RevenueCat and greatly simplifies management. See the guide for more info.
Gets the StoreProduct(s) for the given list of product ids for all product types.
Gets the StoreProduct(s) for the given list of product ids of type type
This function will change the current appUserID. Typically this would be used after a log out to identify a new user without calling configure
Logs out the Purchases client clearing the save appUserID. This will generate a random user id and save it in the cache.
Restores purchases made with the current Play Store account for the current user. This method will post all purchases associated with the current Play Store account to RevenueCat and become associated with the current appUserID
. If the receipt token is being used by an existing user, the current appUserID
will be aliased together with the appUserID
of the existing user. Going forward, either appUserID
will be able to reference the same user.
This method will send all the purchases to the RevenueCat backend. Call this when using your own implementation for subscriptions anytime a sync is needed, such as when migrating existing users to RevenueCat. The onSuccess callback will be called if all purchases have been synced successfully or there are no purchases. Otherwise, the onError callback will be called with a PurchasesError indicating the first error found.