Configuration¶
RevenueCat CLI supports multiple authentication profiles, project-level defaults, and environment variable overrides. This page covers all configuration options.
Authentication Profiles¶
Profiles let you store multiple API keys and switch between them. This is useful when managing staging and production environments, or multiple RevenueCat accounts.
Create a Profile¶
You can optionally bind a default project to a profile:
Switch Profiles¶
List All Profiles¶
View Current Profile¶
Delete a Profile¶
Warning
Deleting a profile removes its stored API key permanently. This action cannot be undone.
Project Configuration¶
Initialize a Project¶
Bind a default project to the current directory:
This creates a .rc.yaml file in the current directory.
.rc.yaml File Format¶
When a .rc.yaml file is present, all commands automatically use that project ID. You can override it per-command with the --project flag.
Tip
Commit .rc.yaml to your repository so your team shares the same project configuration.
Environment Variables¶
Environment variables override profile and file-based configuration. They are especially useful in CI/CD pipelines.
| Variable | Description | Example |
|---|---|---|
RC_API_KEY |
API secret key (overrides active profile) | sk_xxxxx |
RC_PROJECT |
Default project ID | proj_xxxxx |
RC_PROFILE |
Active profile name | production |
RC_OUTPUT |
Default output format | json, table, csv |
RC_DEBUG |
Enable debug logging | true |
RC_TIMEOUT |
HTTP request timeout | 30s |
Precedence Order¶
Configuration is resolved in this order (highest priority first):
- Command-line flags (
--project,--output, etc.) - Environment variables (
RC_PROJECT,RC_OUTPUT, etc.) - Local
.rc.yamlfile - Active auth profile defaults
- Built-in defaults
Note
Flags always win. If you pass --project proj_yyy on the command line, it overrides everything else.
Next Steps¶
Head to the Quick Start to run your first commands.