RevenueCat
RevenueCat manages in-app subscriptions and purchases across iOS, Android, and web, with revenue analytics. The RevenueCat REST API v2 provides programmatic access to projects, apps, customers, paywalls, and audit logs. Nexla connects to the RevenueCat API v2 to ingest subscription and configuration data into your pipelines and to push updates back to your RevenueCat account.
Power end-to-end data operations for your RevenueCat API with Nexla. Our bi-directional RevenueCat connector is purpose-built for RevenueCat, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to RevenueCat or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your RevenueCat workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Before creating a RevenueCat credential, you need to obtain a v2 secret API key from your RevenueCat project. The RevenueCat REST API v2 uses Bearer token authentication: the key is sent in the Authorization header in the form Bearer YOUR_API_KEY. API v1 keys will not work with the v2 API, so you must generate a key specifically for v2.
To obtain a RevenueCat v2 API key, follow these steps:
-
Sign in to the RevenueCat dashboard using your account credentials.
-
Select the project you want to connect, then open the project Settings.
-
Select the API keys section.
-
Click + New to create a new key.
-
Enter a name for the key (e.g., "Nexla Integration").
-
Select V2 as the key version.
-
Configure the permissions (scopes) for the key based on your use case. Each RevenueCat API v2 endpoint documents the specific permissions it requires, so grant only the access levels your pipeline needs.
-
Click Generate to create the key, then copy and store the secret key value securely, as it is used to authenticate your Nexla credential.
The v2 secret API key is sent in the Authorization header for all API requests to the RevenueCat API v2. Treat the key as sensitive information. If your key is compromised, revoke it in the RevenueCat dashboard and generate a new one. For detailed information about authentication, permissions, and available endpoints, see the RevenueCat API v2 Documentation.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| API Key Value | Yes | Yes | An encoded string value used as a secret token to authenticate API requests |
Create a credential in Nexla
-
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Enter your RevenueCat v2 secret API key in the API Key Value field. This is the key you generated in Prerequisites. Nexla sends this value in the
Authorizationheader as a Bearer token for all API requests to the RevenueCat API v2.If your API key is compromised, revoke it in the RevenueCat dashboard and generate a new one. The v2 secret API key grants access to your RevenueCat data based on the permissions configured for the key and should be kept confidential.
For detailed information about authentication, permissions, and available endpoints, see the RevenueCat API v2 Documentation.
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the RevenueCat connector tile, then select the credential that will be used to connect to RevenueCat, and click Next; or, create a new RevenueCat credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common RevenueCat endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
RevenueCat data sources can also be manually configured to ingest data from any valid RevenueCat API v2 endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new RevenueCat data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Use as a destination
Click the + icon on the Nexset that will be sent to the RevenueCat destination, and select the Send to Destination option from the menu. Select the RevenueCat connector from the list of available destination connectors, then select the credential that will be used to connect to RevenueCat, and click Next; or, create a new RevenueCat credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common RevenueCat endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Manual configuration
RevenueCat destinations can also be manually configured to send data to any valid RevenueCat API v2 endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Save & activate
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured RevenueCat endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the RevenueCat endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.