Permute detects test or live mode from the rk_test_ or rk_live_ prefix.
Before you start
- A restricted Stripe API key with read access to the resources you want to sync.
1. Open restricted key setup
In Stripe Dashboard → API Keys, select Create restricted key.
In Stripe Dashboard → API Keys, create a restricted key for Permute. Restricted keys let you choose resource permissions. Select Read for the resources you want to connect. A publishable key cannot read account data, while an unrestricted secret key grants more access than this setup needs.
The setup screen asks you to mark the key as provided to a third-party application and name Permute as the recipient.
2. Choose a third-party application
Choose Providing this key to a third-party application.
3. Name Permute
Enter Permute as the name and https://permute.ai as the URL.
4. Grant read access and copy the key
Set resource permissions to Read, then copy the key.
Stripe restricted keys start with rk_test_ for sandbox data or rk_live_ for live data. Permute detects the environment from that prefix. Test and live modes have separate objects and keys, so a test key will not show live customers or payments.
Check the key prefix before connecting. Use the environment whose data you intend to analyze.
5. Add Stripe in Permute
In your workspace, open Connectors, select Add Connector, choose Stripe, and name the account.
Under Sync which data?, choose an option:
| Choice | What it does |
|---|---|
| Everything | Selects all discovered data available to this connection. |
| Select manually | Choose the tables Permute syncs. |
- Paste the restricted key into API Key and select Connect.
6. Choose tables (manual selection)
If you chose Select manually, open the connector after connecting. Use the checkboxes to select at least one table, then select Save selection.
7. Check the first result
- Choose a Stripe payment or customer in the same test or live mode as the key.
- Check its resource Read permission before comparing the connected data.
Available data
| Data group | What the setup screen covers |
|---|---|
| Money movement | Payments. |
| Relationships | Customers and subscriptions. |
Limit the key to reads
Stripe restricted keys let you choose permissions by resource. The Permute setup screen asks for Read on the resources you want to sync. A publishable key cannot read account records, and a full secret key grants more access than this reporting connection needs.
Review the key’s resource list before copying it. If payments sync but another group is absent, inspect that group’s Read setting in Stripe. Creating a restricted key with a useful name also helps identify it later in the API Keys page.
Read the key prefix
Stripe separates test and live data. A restricted test key begins rk_test_; a restricted live key begins rk_live_. Permute uses that prefix to detect the environment, so the form does not ask for a separate test toggle.
Compare a test key with test customers or payments, and a live key with live ones. If the connection is healthy but every expected production payment is absent, check whether the key begins rk_test_ before changing resource permissions.
Access and source details
Handle key rotation
Stripe’s API Keys page lets you expire and rotate keys. Keep track of whether the connector uses an rk_test_ or rk_live_ key. Use a key of the same mode when rotating, unless you intend to switch from test to live data.
Stripe keeps sandbox and live objects separate, so a mode switch changes which records are visible.
Troubleshooting
| Problem | What to check |
|---|---|
| Live objects are absent | Check that the key starts with rk_live_ rather than rk_test_. |
| One resource is denied | Check its Read permission on the restricted key. |