Connect RevenueCat
RevenueCat supplies subscription revenue and event signals used in recommendation scoring.
Required credential
SpendDaddy requires a RevenueCat REST API v2 secret API key. It must be a
project-level secret key, usually prefixed with sk_.
Do not use any of these in the SpendDaddy API key field:
- A public platform or SDK key such as
appl_...orgoog_... - A RevenueCat API v1 key
- An OAuth token intended for a different integration
RevenueCat's API Keys & Authentication guide explains the difference between public keys and secret API keys. The REST API v2 reference also notes that v1 keys do not work with API v2.
Required API v2 permissions
Create a dedicated V2 secret key with the minimum permissions needed by the Add app flow:
| RevenueCat permission | API operation | Why SpendDaddy needs it |
|---|---|---|
project_configuration:projects:read | List projects | Find the project that contains the app. |
project_configuration:apps:read | List apps in each project | Discover the app and confirm its bundle ID. |
project_configuration:integrations:read | List webhook integrations | Check whether the SpendDaddy webhook already exists. |
project_configuration:integrations:read_write | Create the webhook integration | Configure the app-scoped SpendDaddy webhook automatically. |
In RevenueCat's permission picker, select:
- Project Configuration → Projects: Read
- Project Configuration → Apps: Read
- Project Configuration → Integrations: Read & Write
SpendDaddy does not need customer, subscription, entitlement, product,
offering, chart, or metrics permissions for this integration. A key without
project_configuration:integrations:read_write may validate and find the app,
but automatic webhook setup will fail and must be completed manually.
Generate the key
- Open the RevenueCat dashboard and select the project that contains the app.
- Open Project Settings → API keys.
- Select + New secret API key.
- Give the key a recognizable name, select V2, and apply the permissions listed above.
- Select Generate and copy the secret key.
Keep the key in a server-side secret store. Never put it in a mobile app, browser code, source control, or a support message. RevenueCat's API v2 permissions reference lists the permission names and their scope.
Add it to SpendDaddy
In SpendDaddy, open Add app, choose RevenueCat under Revenue events, and paste the V2 secret key into API key. Select Store credentials and wait for validation.
SpendDaddy uses the key to:
- List projects and apps visible to the key
- Match the RevenueCat app with the App Store Connect and Apple Search Ads app
- Check for an existing SpendDaddy webhook
- Create the app-scoped webhook during app creation when the key has the required integrations write permission
Confirm the displayed app match before creating the app.
Webhook setup
When the key has project_configuration:integrations:read_write, SpendDaddy
configures the RevenueCat webhook automatically during app creation.
If automatic setup is unavailable or fails, SpendDaddy displays a tokenized URL in this form on the webhook step:
https://api.spenddaddy.app/webhooks/revenuecat/<token>
Open the matching RevenueCat project, add a webhook integration for the matched app, and paste that URL. The URL is unique to the app and should be treated as a secret. If you rotate the webhook later, replace the old URL in RevenueCat immediately.
Historical data
New revenue events arrive through the webhook. Historical events can be backfilled by uploading a RevenueCat scheduled export from the setup flow. Large imports may take time to appear while SpendDaddy recalculates metrics.
Validation checklist
- The key is a V2 secret API key, not a public SDK key or v1 key.
- Projects and Apps have read permission.
- Integrations has read/write permission if SpendDaddy should configure the webhook automatically.
- SpendDaddy shows the intended RevenueCat project and app during matching.
- RevenueCat webhook setup reports success, or the manual webhook URL has been added to the matched app.
- Recent revenue-based tiles populate in Overview and recommendation views.