RevenueCat
Connect RevenueCat with a V2 secret API key and your project ID. Fload brings in your subscription metrics and sets up the webhook for you.
What you get
- Subscription revenue, MRR, subscribers, trials and churn for your RevenueCat project, split by store.
- New purchases and renewals as they happen, through a webhook Fload registers itself.
- Your RevenueCat apps linked to your apps in Fload.
Before you start
You need a V2 secret API key for your project. It reads your data and needs one write permission, so Fload can add its webhook:
- Project configuration › Integrations: Read & write. The webhook sends Fload each purchase and renewal as it happens.
- Project configuration › Apps: Read
- Charts & metrics › Overview: Read
- Charts & metrics › Charts: Read
Connect App Store Connect or Google Play first, so Fload can link your RevenueCat apps to your existing apps on its own.
Connect it
- In RevenueCat, go to API Keys and click New secret API key. Create a V2 key with the permissions above, including Integrations: Read & write, and copy it.
- In RevenueCat, open Project Settings, then General settings, and copy your project ID. Use the full ID exactly as shown.
- In Fload, open Connectors, go to the Payments tab, click RevenueCat, then Add Connector.
- Paste the key into Secret API Key and the ID into Project ID.
- Click Test Connection, then Connect.
- Fload starts syncing. Watch it finish, or click Continue in background.
You don't need to set up a webhook in RevenueCat: Fload registers it for you. Leave Webhook Auth Header (under Advanced) blank unless you want to reuse a webhook secret you already have.
What Fload reads
| Data | Detail |
|---|---|
| Revenue | Per store: App Store, Google Play and web billing |
| Subscribers | Active subscriptions and trials |
| Trials and conversion | Trial starts and how many convert to paid |
| MRR, retention and churn | How recurring revenue and subscribers hold up |
| Purchase events | New purchases and renewals, as they happen |
Apart from adding its webhook, Fload only reads. It never changes your products, offerings or customers.
When data arrives
- Purchase and renewal events arrive through the webhook as they happen.
- RevenueCat's charts refresh about every four hours.
- Until the first data lands, the card says No data received yet.
Fix a problem
Test Connection fails Check that the key is a V2 secret key with the permissions above, and that the project ID is copied in full.
Fload asks you to let it add its webhook Your key can read but not add the webhook, so Fload opens a card in your Inbox and emails your organization's owners. To fix it:
- In RevenueCat, open API Keys and give the key Fload uses Project configuration › Integrations: Read & write.
- Press Check again on the card. Fload adds the webhook right away and the card closes.
Can't change that key? Connect RevenueCat again in Connectors with a new key that has the permission. Fload adds its webhook to the new connection. Then remove the old connection, and the card closes.
You can also add the webhook yourself in RevenueCat under Integrations › Webhooks, using the URL on the card. Ask Fload support for its authorization header, then press Check again. Fload finds the webhook as long as the key can at least read Integrations.
Data shows on the wrong app Choose Configure from the card's menu and link each RevenueCat app to the right app in Fload.