Connect
RevenueCat
RevenueCat connects with a project-scoped secret API key (v2) rather than OAuth. You generate the key in the RevenueCat dashboard and paste it into Modiva. The key is scoped to a single project, so Modiva auto-detects that project — you don't need to enter its id.
Before you start
- A RevenueCat account with at least one project configured.
- A secret API key with API version 2, created under Project settings → API keys → Secret API keys.
Step-by-step setup
- 1
Create a secret API key (v2)
In the RevenueCat dashboard open your project, go to API keys in the left sidebar, and under "Secret API keys" click "+ New secret API key". Give it a label like "Modiva", make sure it uses API Version 2, and copy the generated sk_… value — you won't be able to see it again. Secret keys are powerful, so never expose them in front-end code or public repos.
- 2
Sign in to Modiva
Log in at modiva.ai and open the Dashboard. You need a Modiva account before you can connect any platform — creating one takes a minute and no credit card is required for the free tier.
The Modiva dashboard — your home for connections, posts and analytics. - 3
Open Connections → New connection
In the left sidebar choose Connections, then click New connection. You'll see the full catalogue of platforms grouped by category (Social, Ads and CRM).
The connection picker. Use the search box or category filter to find your platform. - 4
Paste the secret key
Click the RevenueCat card. In the inline form paste the sk_… secret key. Leave Project ID blank to let Modiva auto-detect it, or set it explicitly if you prefer. Click Connect.
- 5
You're connected
Modiva validates the key against the RevenueCat v2 API and shows the connection as Connected. If the key is wrong or lacks v2 access you'll see an error — re-check the key and try again.
Permissions Modiva requests
When you connect RevenueCat, Modiva asks only for the access it needs to run the tools you use. You can revoke it any time from RevenueCat or by disconnecting in Modiva.
- Read the project, its apps and products
- Read entitlements, offerings and packages
- Read customers, their subscriptions and purchases
Troubleshooting & FAQ
Why a secret API key instead of OAuth?
RevenueCat's v2 REST API authenticates with a project secret key, which works today with no extra setup. RevenueCat also offers an OAuth flow for technology partners; Modiva can move to that in the future without changing how the tools work.
Which project does the connection cover?
A v2 secret key belongs to exactly one RevenueCat project. Modiva reads that project automatically from the key, so every tool is scoped to it. To connect another project, create a secret key in that project and add a second connection.
Can Modiva change my subscriptions or customers?
No. The RevenueCat tools are read-only today — they list and fetch products, entitlements, offerings, packages, customers, subscriptions and purchases. Write operations are not exposed.
How do I revoke Modiva's access?
Delete the "Modiva" secret API key in the RevenueCat dashboard under API keys, then Disconnect the connection in Modiva.
Need help with RevenueCat?
Fin can answer follow-up questions and walk you through any step.
RevenueCat playbooks
Connected? Put RevenueCat to work with these free growth playbooks.