How do I connect my app to RevenueDot?

Install the RevenueDot SDK for your platform and pass your app's API key to configure. On RevenueDot Cloud that is all the setup, because the SDK already calls https://api.revenuedot.app. This is the way for new apps. It is also the way for any app that wants the SDK to verify that each response came from RevenueDot and to send nothing to RevenueCat's hosts. An app that already ships the RevenueCat SDK can instead keep it and set one line, the proxy URL. When such an app switches, the importer lets versions already in users' hands keep their RevenueCat API keys.

Install the RevenueDot SDK and pass your key#

// iOS: Swift package github.com/revenuedot/purchases-ios at 5.91.0-revenuedot, or pod 'RevenueDotPurchases', '5.91.0'.
import RevenueCat

Purchases.configure(withAPIKey: "appl_...")

// Android: implementation("app.revenuedot.purchases:purchases:10.23.3"), then in Application.onCreate():
Purchases.configure(PurchasesConfiguration.Builder(this, "goog_...").build())

// React Native and Expo: npm install react-native-purchases@npm:@revenuedot/react-native-purchases@10.10.2
import { Platform } from "react-native";
import Purchases from "react-native-purchases";

Purchases.configure({ apiKey: Platform.OS === "ios" ? "appl_..." : "goog_..." });

The RevenueDot SDK is built from RevenueCat's open-source SDK (MIT license), so your code imports RevenueCat and calls Purchases. It sends every request to RevenueDot and needs no RevenueCat account. It keeps the names your code imports (import RevenueCat, com.revenuecat.purchases.*, package:purchases_flutter). These changes matter to your app:

• Each SDK calls https://api.revenuedot.app (RevenueDot Cloud) by default, so a Cloud project needs no proxy URL.
• Each SDK trusts RevenueDot's response-signing key, so entitlement verification reports VERIFIED against RevenueDot Cloud.
• The Android SDK and purchases-js send their diagnostics and events to RevenueDot too.
• The proxy URL works on Flutter web.

There is a RevenueDot SDK for iOS, Android, React Native and Expo, Flutter, the web, Capacitor and Ionic, Kotlin Multiplatform, Unity and Cordova. The install line for each one is in Which SDKs does RevenueDot have?: CocoaPods and Swift packages for iOS, Maven Central for Android and Kotlin Multiplatform, npm for the web, React Native, Capacitor and Cordova, a git tag for Flutter, and OpenUPM for Unity.

Self-hosting: also set the SDK's proxy URL to your server before configure, and set entitlement verification to disabled. A self-hosted server signs with its own key, so the official builds only verify against RevenueDot Cloud. The iOS, Android, Capacitor and Unity SDKs default to informational mode, which would log every response from your server as a failed check, so they need the setting. React Native, Flutter and Kotlin Multiplatform already default to disabled. Cordova has no setting for it, so it logs the failed checks and still grants access. Each SDK guide shows the code. To verify against your own server, build the SDKs with your key; see Trusted Entitlements.

Switching from RevenueCat? Keep your SDK and set one line#

An app that already ships the RevenueCat SDK can keep it. Set the SDK's proxy URL to RevenueDot (https://api.revenuedot.app for RevenueDot Cloud, or your own server) and turn its signature check off. That is proxy mode, and it works with every RevenueCat app SDK.

Watch the 1:18 walkthrough of proxy mode, or on YouTube. Watch page.

// iOS. Keep the RevenueCat SDK and point it at your RevenueDot server; nothing else in the app changes.
Purchases.proxyURL = URL(string: "https://revenuedot.example.com")!
Purchases.configure(with: Configuration.Builder(withAPIKey: "appl_...").with(entitlementVerificationMode: .disabled).build())

// Android. Keep the RevenueCat SDK and point it at your RevenueDot server; nothing else in the app changes.
Purchases.proxyURL = URL("https://revenuedot.example.com")
Purchases.configure(PurchasesConfiguration.Builder(context, "goog_...").entitlementVerificationMode(EntitlementVerificationMode.DISABLED).build())

// React Native and Expo. Keep the RevenueCat SDK and point it at your RevenueDot server; nothing else in the app changes.
import { Platform } from "react-native";
import Purchases from "react-native-purchases";

await Purchases.setProxyURL("https://revenuedot.example.com");
Purchases.configure({ apiKey: Platform.OS === "ios" ? "appl_..." : "goog_..." });

• Set the proxy URL before configure. The SDK reads it once. For RevenueDot Cloud it is https://api.revenuedot.app.
• Turn entitlement verification off. The RevenueCat SDK checks responses against RevenueCat's signing key. RevenueDot cannot sign with that key, so iOS and Android would report every response as FAILED in their default informational mode. Access still works, but the logs fill with errors. See Trusted Entitlements.
• Use the keys RevenueDot gives each app (appl_, goog_, test_ ...), or keep your RevenueCat keys as described below.
• Known limits. The RevenueCat Android SDK still sends diagnostics, paywall events and ad events to RevenueCat's hosts. RevenueCat's purchases-js sends analytics to RevenueCat unless you set flags: { collectAnalyticsEvents: false }. Flutter's web build ignores the proxy URL.
• You can swap in the RevenueDot SDK later, in any release. It is a package change, because it keeps every import name.

Every SDK's exact call is in its guide: iOS, Android, React Native, Flutter, Web, Capacitor, Kotlin Multiplatform, Unity, Cordova.

Keep your RevenueCat API keys#

Apps already in the store send their RevenueCat public key (appl_..., goog_...). The importer sets each RevenueDot app's public key to that same string, so old app versions work against RevenueDot the moment you point traffic at it. You can also do it for one app with the API:

curl -s -X POST "$REVENUEDOT_URL/v2/projects/$PROJECT_ID/import/apps/$APP_ID/public_key" \
  -H "Authorization: Bearer $SECRET_KEY" -H "Content-Type: application/json" \
  -d '{"public_key":"appl_YourExistingRevenueCatKey"}'

Old app versions still call RevenueCat's API until they update, because the proxy URL lives in the app. That is why a migration runs both systems side by side for a while. See Migrate from RevenueCat.

New apps install the RevenueDot SDK; switching apps can start with one line#

• New app, or new to in-app purchases: install the RevenueDot SDK and test with the Test Store. See the Quickstart.
• Already selling with your own StoreKit or Google Play Billing code: import your products from App Store Connect, Google Play or Stripe, install the RevenueDot SDK, and call syncPurchases() once on the first launch of the update. It sends the device's existing store purchases to RevenueDot, so current subscribers keep access. Store notifications keep them current after that.
• You rely on entitlement verification: install the RevenueDot SDK. When you self-host, build it with your server's key.
• Self-hosting: install the RevenueDot SDK, set its proxy URL to your server and set entitlement verification to disabled.
• Moving a live app from RevenueCat: use proxy mode or the RevenueDot SDK in the next release, keep your RevenueCat keys through the importer, and run both systems side by side in a dual run until most users have updated.

Related#

• Quickstart
• SDK guides
• Which key goes where
• Why we forked the RevenueCat SDKs