Docs

Connect every service

Each service needs one read-only key. Here's which key, on which plan, how long it takes and whether you'll see billed or estimated cost. Every key goes straight into your computer's keychain.

On this page

Connect everything with your AI assistant

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It goes through your services one at a time.

Help me create read-only keys for Burnstack, one service at a time. First ask me which of the services below I use. Then, for each one I pick, in turn: open its key page, set only the permissions listed for it and a 90-day expiry where the service offers one, and stop before the final button that creates the key (Generate, Create, Add…). Tell me it's ready. I'll click it, copy the key and paste it into Burnstack myself. Don't copy, read or paste any key, token or secret, and don't grant broader access or change any other setting. If a service asks me to sign in or confirm with 2FA, wait for me. Wait until I say I've pasted the key into Burnstack before moving to the next service. If a page looks different from what's listed here, describe it to me instead of guessing.

Key pages and minimum permissions:
- Vercel: https://vercel.com/account/tokens (Scope: your team → All Projects)
- Neon: https://console.neon.tech/ (Organization API key (not Project-scoped); only org admins can create one)
- Supabase: https://supabase.com/dashboard/account/tokens (Organization Settings: Read; Organization Projects: Read)
- Anthropic: https://platform.claude.com/settings/admin-keys (Admin key (no selectable scopes); needs the organization admin role)
- OpenAI: https://platform.openai.com/settings/organization/admin-keys (Permissions: Restricted; Usage API: Read; Organization Administration: Read)
- GitHub: https://github.com/settings/personal-access-tokens/new (Account permissions → Plan: Read-only (your personal account); Organization permissions → Administration: Read-only (an organization's billing; org admins only))
- OpenRouter: https://openrouter.ai/settings/management-keys (Management key (OpenRouter has no narrower scope))
- DigitalOcean: https://cloud.digitalocean.com/account/api/tokens (Custom Scopes: account:read; billing:read)
- Stripe fees: https://dashboard.stripe.com/apikeys (Balance: Read; Every other permission: None)
- Twilio: https://1console.twilio.com/go?to=/account/__account__/settings/us1/api-keys/list (Key type: Restricted; /twilio/billing/usage/read)
- Cloudflare: https://dash.cloudflare.com/profile/api-tokens (Account → Billing → Read)
- Netlify: https://app.netlify.com/user/applications#personal-access-tokens (No scopes: the token can do what your user can (Burnstack only reads))
- Datadog: https://app.datadoghq.com/organization-settings/application-keys (Application key scopes: usage_read, billing_read; Your role: Usage Read and Billing Read)
- Sentry: https://sentry.io/orgredirect/organizations/:orgslug/settings/developer-settings/ (Organization: Read (org:read))
- AWS: https://console.aws.amazon.com/iam/home#/users (Inline policy: ce:GetCostAndUsage on Resource *)
- Cursor: https://cursor.com/dashboard/api (Admin API key (admin:*); team admins only)
- PlanetScale: https://app.planetscale.com/~/settings/service-tokens (read_invoices; read_organization (optional, shows the plan))
- Microsoft Azure: https://portal.azure.com/#view/Microsoft_AAD_RegisteredApps/ApplicationsListBlade (Cost Management Reader (on the subscription))
- Google Cloud: https://console.cloud.google.com/billing/export (BigQuery Data Viewer (on the export dataset); BigQuery Job User (on the project))
- MongoDB Atlas: https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%23%2Forg%2F%3Corganization%3E%2Faccess%2FserviceAccounts (Organization Billing Viewer)
- Railway: https://railway.com/account/tokens (Workspace: your workspace (a workspace token; no narrower scopes))
- Render: https://dashboard.render.com/u/settings#api-keys (API key (Render keys can't be scoped or made read-only))
- Heroku: https://dashboard.heroku.com/account/applications (Scopes: identity, read (both read-only))
- Akamai (Linode): https://cloud.linode.com/profile/tokens (Account: Read Only; Everything else: No Access)
- Vultr: https://my.vultr.com/settings/#settingsapi (User permissions: Billing only; API access enabled)
- Fastly: https://manage.fastly.com/account/personal/tokens (Scope: global:read; User role: Billing (or Superuser))
- Runpod: https://console.runpod.io/user/credentials (Permission: Read Only)
- xAI: https://console.x.ai/ (Management key for the team (no read-only option is documented))
- Together AI: https://api.together.ai/settings/api-keys (API key (Together keys have no read-only option))
- fal.ai: https://fal.ai/dashboard/keys (Preset: BILLING (billing:usage:read, auth:keys:read, account:users:read))
- Runway: https://dev.runwayml.com/ (API key of the project (Admin or Developer role to create; no read-only option))
- Upstash: https://console.upstash.com/account/api (Permission: Read Only)
- Ramp: https://app.ramp.com/settings/ramp-developer/apps (Grant type: Client credentials; Scope: transactions:read)
- Brex: https://dashboard.brex.com/settings/developer (transactions.card.readonly (View card transaction data))
- Mercury: https://app.mercury.com/settings/tokens (Permission tier: Read Only)

This prompt, and the one in each service's guide:

  • Opens the vendor's key page and sets only the minimum permissions, with a 90-day expiry where the vendor offers one.
  • Stops before the final Generate/Create click and says it's ready.
  • The person creates the key and pastes it into Burnstack; the key never passes through the AI or the chat.
  • Grants nothing broader and changes no other setting.
  • Waits for the person whenever the vendor asks for sign-in or 2FA.

not yet verified marks a detail not yet checked against the service's current site. The rest is.

Hosting & edge

ServiceKeyPlanDataTimeSetup
Vercel Access token Pro or Enterprise team; your role must see billing (Owner, Member, Developer, Security, Billing or Enterprise Viewer). Billed 2 min Connect it to Vercel →
DigitalOcean Personal access token Any team; your role must be able to see billing. Billed 2 min Connect it to DigitalOcean →
Cloudflare API token Pay-as-you-go accounts (Free, Pro, Business); Enterprise contracts get plan fees only. Billed 3 min Connect it to Cloudflare →
Netlify Personal access token Any plan. Exact charges need invoice imports; the API has no billing data. Estimated 2 min Connect it to Netlify →
Railway Workspace token Any plan; your role must see the workspace's billing. Estimated 2 min Connect it to Railway →
Render API key Any workspace plan; the key sees every workspace your account belongs to. Estimated 2 min Connect it to Render →
Heroku Authorization token (identity, read) Any account; a team's invoices need a role that can see them. Billed 3 min Connect it to Heroku →
Fastly API token (global:read) Any paid account; the token's user needs the Billing or Superuser role. Billed 2 min Connect it to Fastly →

Databases

ServiceKeyPlanDataTimeSetup
Neon Organization API key A paid plan (Launch, Scale, Business or Enterprise) for usage data; free orgs connect but have nothing billable. Estimated 2 min Connect it to Neon →
Supabase Organization slug and access token Any plan. Usage-based charges need invoice imports; the API has no billing data. Estimated 3 min Connect it to Supabase →
PlanetScale Service token Any plan. Billed 3 min Connect it to PlanetScale →
MongoDB Atlas Organization ID and service account Any organization; an Organization Owner creates the service account. Billed 5 min Connect it to MongoDB Atlas →
Upstash Email and Developer API key (Read Only) Any account with Redis databases. Billed 2 min Connect it to Upstash →

AI providers

ServiceKeyPlanDataTimeSetup
Anthropic Admin API key An organization, not an individual account (the Admin API is unavailable for individual accounts). Billed 2 min Connect it to Anthropic →
OpenAI Admin key Any paid API organization; only Owners can create Admin keys. Billed 2 min Connect it to OpenAI →
OpenRouter Management key Any account; in an organization, only Organization Admins can create one. Billed 2 min Connect it to OpenRouter →
Cursor Admin API key Enterprise teams (Cursor lists the Admin API for Enterprise). Billed 2 min Connect it to Cursor →
Runpod API key (Read Only) Any account (personal or team). Billed 2 min Connect it to Runpod →
xAI Management key Any team with API usage. Billed 2 min Connect it to xAI →
Together AI API key An organization with the billing usage API (beta) enabled by Together support. Billed 2 min Connect it to Together AI →
fal.ai API key (BILLING preset) Any account. Billed 2 min Connect it to fal.ai →
Runway API key Any Runway API (developer portal) project. Billed 2 min Connect it to Runway →
Gemini API & Vertex AI Billed through Google Cloud: connect Google Cloud (billing export) and they show up as services of each project. Billed 15 min Connect Google Cloud →
Azure OpenAI Billed through Azure: connect Microsoft Azure and it shows up as Cognitive Services in its resource group (not split by model yet). Billed 8 min Connect Microsoft Azure →
Amazon Bedrock Billed through AWS: connect AWS and Bedrock shows up as a service per account (not split by model yet). Billed 5 min Connect AWS →

Cloud

ServiceKeyPlanDataTimeSetup
AWS IAM user access key Any account with Cost Explorer enabled; use the management account to see an organization. $0.01 per Cost Explorer request (about $1/month). Billed 5 min Connect it to AWS →
Microsoft Azure Service principal and subscription ID Pay-as-you-go, EA, MCA, MSDN or Visual Studio subscriptions billed in USD. EA needs "Account owners can view charges"; MCA needs the "Azure charges" policy on. Billed 8 min Connect it to Microsoft Azure →
Google Cloud Billing export table and service account JSON key A USD Cloud Billing account; you need Billing Account Administrator or Costs Manager to turn on the export. Billed 15 min not yet verified Connect it to Google Cloud →
Akamai (Linode) Personal access token (Account: Read Only) Any account; a restricted user needs billing access. Billed 2 min Connect it to Akamai (Linode) →
Vultr API key of a billing-only user Any account; the key's user needs the Billing permission. Billed 4 min Connect it to Vultr →

Dev tools & monitoring

ServiceKeyPlanDataTimeSetup
GitHub Fine-grained personal access token Any plan, on GitHub's enhanced billing platform. Billed 2 min Connect it to GitHub →
Twilio Account SID, API key SID and secret Any USD-billed account. Restricted keys are US1-only. Billed 3 min Connect it to Twilio →
Datadog Site, API key and application key Pro or Enterprise, keys from the parent organization. Billed 4 min Connect it to Datadog →
Sentry Organization slug and auth token Any plan. Sentry reports event counts, not dollars: import invoices for costs. Usage + invoice import 3 min Connect it to Sentry →

Payments & cards

ServiceKeyPlanDataTimeSetup
Stripe fees Restricted key Any Stripe account with a USD balance. Billed 3 min Connect it to Stripe fees →
Ramp Client ID and client secret (developer app) Any Ramp business; an admin (or business owner) creates the developer app. Billed 4 min Connect it to Ramp →
Brex User token Any Brex account. An account admin or card admin creates the token; a regular user's token only sees their own charges. Billed 2 min Connect it to Brex →
Mercury Read Only API token Any Mercury account; your user needs permission to create API tokens (usually an admin). Billed 2 min Connect it to Mercury →

Revenue

ServiceKeyPlanDataTimeSetup
Stripe (revenue) Restricted key Any Stripe account, in any balance currency (converted at ECB reference rates). Reported 3 min Connect it to Stripe (revenue) →
Paddle (revenue) API key Any Paddle Billing account (live or sandbox). Paddle Classic accounts use a different API and aren't supported. Reported 3 min Connect it to Paddle (revenue) →
RevenueCat (revenue) Secret API key (V2) Any RevenueCat project. One connection per project; each project has its own keys. Reported 3 min Connect it to RevenueCat (revenue) →
Lemon Squeezy (revenue) API key Any Lemon Squeezy store. A key sees every store of its user; use a live-mode key (test-mode keys return test orders). Fees estimated 2 min Connect it to Lemon Squeezy (revenue) →
Polar (revenue) Organization access token Any Polar organization in production (sandbox tokens aren't supported). Reported 2 min Connect it to Polar (revenue) →
App Store (revenue) Team API key (Issuer ID, Key ID, vendor number, .p8) An Apple Developer Program membership with paid apps or in-app purchases, and an Admin to create the team key. Apple Pay is a payment method inside Stripe, Paddle and the like, not this; App Store is the store that pays app developers. Reported 5 min Connect it to App Store (revenue) →
Google Play (revenue) Reports bucket and service account JSON key A Google Play developer account with paid apps or in-app purchases; the Play Console owner or an admin invites the service account. Google Pay is a payment method inside Stripe and the like, not this; Google Play is the store that pays app developers. Reported 10 min Connect it to Google Play (revenue) →
PayPal (revenue) REST app client ID and secret A PayPal Business account with access to the developer dashboard. Sandbox apps work too: add the word sandbox to what you paste. Reported 5 min Connect it to PayPal (revenue) →

Receipts only

No billing API, so there's no key: import their invoices instead, and nothing counts until you approve it. How imports work.

ServiceHow
Fly.ioNo billing API: drop Fly.io's invoice PDF on the Imports page, which reads it line by line.
FigmaNo billing API: send Figma's invoice (PDF or CSV export) through the Imports page.
NotionNo billing API: send Notion's invoice (PDF or CSV export) through the Imports page.
LinearNo billing API: send Linear's invoice (PDF or CSV export) through the Imports page.
SlackNo billing API: send Slack's invoice (PDF or CSV export) through the Imports page.
Google WorkspaceNo billing API: send Google Workspace's invoice (PDF or CSV export) through the Imports page.
AtlassianNo billing API: send Atlassian's invoice (PDF or CSV export) through the Imports page.

AI apps (MCP)

Let an AI app read your spend summary, trends and alerts. It's off until you turn it on in Burnstack, and what the app reads goes to its AI provider. More about AI apps.

Replace <path> with the path to Burnstack's MCP server. Settings → AI apps (MCP) in Burnstack shows the exact path on your computer and gives you these snippets with it filled in. By default it's /Applications/Burnstack.app/Contents/MacOS/burnstack-mcp on a Mac and %LOCALAPPDATA%\Burnstack\burnstack-mcp.exe on Windows.

Claude Desktop

Install the Burnstack extension (.mcpb), or Settings → Developer → Edit Config, merge this into claude_desktop_config.json and restart Claude Desktop.

{"mcpServers": {"burnstack": {"command": "<path>"}}}

Claude Code

Run in a terminal. --scope user makes it work in every project; leave it out for the current one only.

claude mcp add --scope user burnstack -- <path>

Cursor

Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in a project.

{"mcpServers": {"burnstack": {"command": "<path>"}}}

VS Code

Add to .vscode/mcp.json in a workspace, or run "MCP: Open User Configuration" from the Command Palette.

{"servers": {"burnstack": {"type": "stdio", "command": "<path>"}}}

Ramp

Connect it: Ramp

About 4 minBilled

Need

  • Key: Client ID and client secret (developer app)
  • Plan: Any Ramp business; an admin (or business owner) creates the developer app.
  • Permissions: Grant type: Client credentials Scope: transactions:read

A Ramp admin creates a developer app (Company → Developer) with the Client credentials grant type and only the transactions:read scope. Paste CLIENT_ID:CLIENT_SECRET. Burnstack reads every card transaction on this computer and keeps only dev, SaaS and AI charges; groceries, travel and everything else are dropped without being stored, and nothing leaves this computer.

Steps

Open Ramp's key page ↗

  1. As a Ramp admin, open Company → Developer and click Create new app (Start building for a first app).
  2. Name it Burnstack and accept the Terms.
  3. Under Grant types, make sure Client credentials is on.
  4. Under Scopes, click Configure allowed scopes and select transactions:read only.
  5. Paste CLIENT_ID:CLIENT_SECRET into Burnstack.

Paste it

In Burnstack: Connectors → Ramp → Add key → paste → Validate & save. The key goes straight into your computer's keychain.

If it fails

invalid_scope
The app doesn't allow transactions:read yet. Under Scopes, click Configure allowed scopes, select transactions:read, save, and try again.
Ramp API error 403
The token is valid but lacks transactions:read. Add the scope to the app under Scopes → Configure allowed scopes.
invalid_client not yet verified
The client ID or secret is wrong, or the secret was rotated. Copy both from the app's page and paste CLIENT_ID:CLIENT_SECRET.

Let your AI do the clicking not yet verified

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Ramp's key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://app.ramp.com/settings/ramp-developer/apps in my browser. Choose 'Create new app' (or 'Start building' if it's the first app), name it 'Burnstack' and accept the Terms. Ramp has no expiry setting for this client secret, so skip that. Stop before clicking 'Create' (the final button that creates the client secret) and tell me it's ready. I'll click it, copy the client secret and paste it into Burnstack myself. Don't copy, read or paste the client secret, and don't grant broader access or change any other setting. After I say I've copied the Client ID and Client Secret, check that 'Grant types' includes 'Client credentials', then under 'Scopes' choose 'Configure allowed scopes', select only 'transactions:read' and save. If Ramp asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Billed: Billed cost, as Ramp charges it.
  • History: Every card transaction; the first sync reads the last 90 days.
  • Delay: Near real time. Charges count once they clear (pending ones wait); the last 13 days are re-read every sync.

Brex

Connect it: Brex

About 2 minBilled

Need

  • Key: User token
  • Plan: Any Brex account. An account admin or card admin creates the token; a regular user's token only sees their own charges.
  • Permissions: transactions.card.readonly (View card transaction data)

An account admin or card admin creates a user token under Developer → Settings with only the transactions.card.readonly scope (View card transaction data). Burnstack reads every settled card transaction on this computer and keeps only dev, SaaS and AI charges; everything else is dropped without being stored, and nothing leaves this computer. Brex expires tokens that go unused for 90 days.

Steps not yet verified

Open Brex's key page ↗

  1. Sign in to the Brex dashboard as an account admin or card admin and open Developer → Settings.
  2. Click Create Token and name it Burnstack.
  3. For data access, choose only card transactions, read-only (transactions.card.readonly).
  4. Check the summary and click Allow Access.
  5. Copy the token (bxt_…, shown once) and paste it into Burnstack.

Paste it

In Burnstack: Connectors → Brex → Add key → paste → Validate & save. The key goes straight into your computer's keychain.

If it fails

Brex API error 401
The token was revoked, mistyped, or expired after 90 days without use. Create a new user token.
Brex API error 403
The token lacks transactions.card.readonly. Create a new token with that scope.

Let your AI do the clicking not yet verified

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Brex's key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://dashboard.brex.com/settings/developer in my browser. Choose 'Create Token' and name it 'Burnstack'. For the data access it asks about, select only card transactions read-only ('transactions.card.readonly', View card transaction data) and nothing else. Brex has no expiry setting for this token, so skip that. Stop before clicking 'Allow Access' (the final button that creates the token) and tell me it's ready. I'll click it, copy the token and paste it into Burnstack myself. Don't copy, read or paste the token, and don't grant broader access or change any other setting. If Brex asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Billed: Billed cost, as Brex charges it.
  • History: Every settled card transaction; the first sync reads the last 90 days.
  • Delay: Settled transactions only, usually a day or two after the purchase; the last 13 days are re-read every sync.

Mercury

Connect it: Mercury

About 2 minBilled

Need

  • Key: Read Only API token
  • Plan: Any Mercury account; your user needs permission to create API tokens (usually an admin).
  • Permissions: Permission tier: Read Only

In Mercury, a user who may create API tokens (usually an admin) opens Settings → Tokens and creates a token with the Read Only permission tier, which needs no IP allowlist. Paste it with its secret-token: prefix. Burnstack reads card and bank transactions on this computer and keeps only dev, SaaS and AI charges; transfers, payroll and everything else are dropped without being stored, and nothing leaves this computer. Mercury deletes tokens that go unused for 45 days.

Steps

Open Mercury's key page ↗

  1. Click your organization at the top left, then All Settings → Tokens.
  2. Click Create an API Token and name it Burnstack.
  3. Choose the Read Only permission tier (it needs no IP allowlist).
  4. Create it and copy the token (secret-token:mercury_production_…, shown once).
  5. Paste it into Burnstack.

Paste it

In Burnstack: Connectors → Mercury → Add key → paste → Validate & save. The key goes straight into your computer's keychain.

If it fails

No 'Create an API Token' button
Your Mercury user can't create tokens. Sign in as an admin, or ask one to raise your permissions.
Mercury API error 401 not yet verified
The token was revoked, mistyped, or deleted after 45 days without use. Create a new Read Only token and paste it with its secret-token: prefix.

Let your AI do the clicking not yet verified

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Mercury's key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://app.mercury.com/settings/tokens in my browser. Choose 'Create an API Token', name it 'Burnstack' and pick the 'Read Only' permission tier, nothing broader. Mercury has no expiry setting for this token, so skip that. Stop before clicking 'Create' (the final button that creates the token) and tell me it's ready. I'll click it, copy the token and paste it into Burnstack myself. Don't copy, read or paste the token, and don't grant broader access or change any other setting. If Mercury asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Billed: Billed cost, as Mercury charges it.
  • History: Every transaction; the first sync reads the last 90 days.
  • Delay: Charges count once they're posted (status sent); pending ones wait. The last 13 days are re-read every sync.

Stripe (revenue)

Connect it: Stripe (revenue)

About 3 minReported

Need

  • Key: Restricted key
  • Plan: Any Stripe account, in any balance currency (converted at ECB reference rates).
  • Permissions: Balance Transaction Sources: Read Charges and Refunds: Read Invoices: Read (optional) Products: Read (optional) Payment Disputes: Read (optional) Every other permission: None

Create a restricted key (rk_…) with the Read permissions listed here and every other permission set to None. Secret keys (sk_…) are refused because they can do anything in your account. Stripe fees will come from this connection on the Profit page; your Stripe fees connector keeps showing them as spend.

Steps

Open Stripe (revenue)'s key page ↗

  1. Open Developers → API keys and click Create restricted key.
  2. Start from zero permissions and name it Burnstack revenue.
  3. Set Balance Transaction Sources and Charges and Refunds to Read.
  4. For products and subscription periods, also set Invoices, Products and Payment Disputes to Read; leave every other permission at None.
  5. Click Create key, complete Stripe's two-step verification, then copy the key (rk_live_…).
  6. Paste it into Burnstack under Connectors → Add revenue.

Paste it

In Burnstack: Connectors → Add revenue → Stripe → Add key → paste → Validate & save. The key goes straight into your computer's keychain. Revenue tracking needs the free beta license: Activate free on the Profit page.

If it fails

This is a secret key (sk_…), which has full access to your Stripe account
Create a restricted key (rk_…) with only the Read permissions listed.
Stripe API error 401: Invalid API Key provided
The key was rolled, deleted or mistyped. Create a new restricted key.
Stripe API error 403: The provided key does not have the required permissions not yet verified
Burnstack adds the permission to give the key: edit the key (⋯ → Edit key) and set it to Read.

Let your AI do the clicking

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Stripe (revenue)'s key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://dashboard.stripe.com/apikeys in my browser. Choose 'Create restricted key' and start from zero permissions, not a preconfigured set. Enter 'Burnstack revenue' as the Key name. Set Balance Transaction Sources, Charges and Refunds, Invoices, Products and Payment Disputes to Read and leave every other permission at None. Stripe has no expiry setting for this key, so skip that. Stop before clicking 'Create key' (the final button that creates the key) and tell me it's ready. I'll click it, copy the key and paste it into Burnstack myself. Don't copy, read or paste the key, and don't grant broader access or change any other setting. If Stripe asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Reported: From Stripe's own sales data. Anything Burnstack has to estimate until Stripe settles it is marked provisional.
  • History: No documented limit; the first sync covers 400 days, so annual plans sold last year still count.
  • Delay: Sales, refunds and fees appear as Stripe creates their balance transactions; payouts when Stripe sends them.

Paddle (revenue)

Connect it: Paddle (revenue)

About 3 minReported

Need

  • Key: API key
  • Plan: Any Paddle Billing account (live or sandbox). Paddle Classic accounts use a different API and aren't supported.
  • Permissions: Transactions: Read (transaction.read) Adjustments: Read (adjustment.read) Products: Read (product.read, optional) Reports: Read (report.read, optional; report.write lets Burnstack create the payout report itself) Every other permission: none

Create an API key with only the Read permissions listed here; keys that can write anything are refused. Paddle is the merchant of record: it collects and pays the tax on your sales, so tax shows as its own step on the Profit page. Paddle keys expire (90 days by default, at most a year): when yours does, use Replace key.

Steps not yet verified

Open Paddle (revenue)'s key page ↗ not yet verified

  1. In Paddle, open Developer tools → Authentication and choose the API keys tab.
  2. Click New API key and name it Burnstack revenue.
  3. Under permissions, give Read to Transactions and Adjustments, and to Products and Reports for product names and payouts. Give nothing Write.
  4. Keep the expiry date at 90 days, click Save, then copy the key (pdl_live_apikey_…, shown once).
  5. Paste it into Burnstack under Connectors → Add revenue.

Paste it

In Burnstack: Connectors → Add revenue → Paddle → Add key → paste → Validate & save. The key goes straight into your computer's keychain. Revenue tracking needs the free beta license: Activate free on the Profit page.

If it fails

This API key can change your Paddle account
The key has a Write permission. Create a new key with only the Read permissions listed.
This is a legacy Paddle API key
Keys made before May 2025 can't be limited. Create a new API key with only the Read permissions listed.
The API key lacks the adjustment.read permission
Create a key that also has Read on Adjustments (refunds and chargebacks need it).
Paddle API error 403: invalid_token not yet verified
The key expired or was revoked (keys last 90 days by default). Create a new one and use Replace key.

Let your AI do the clicking not yet verified

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Paddle (revenue)'s key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://vendors.paddle.com/authentication-v2 in my browser. Choose the API keys tab and click 'New API key'. Enter 'Burnstack revenue' as the name. Under permissions give Read (and nothing else) to Transactions, Adjustments, Products and Reports; leave every other permission off and give nothing Write. Set Expiry date to 90 days (or the closest shorter option). Stop before clicking 'Save' (the final button that creates the API key) and tell me it's ready. I'll click it, copy the API key and paste it into Burnstack myself. Don't copy, read or paste the API key, and don't grant broader access or change any other setting. If Paddle asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Reported: From Paddle's own sales data. Anything Burnstack has to estimate until Paddle settles it is marked provisional.
  • History: No documented limit; the first sync covers 400 days, so annual plans sold last year still count.
  • Delay: Sales count once they're paid; Paddle's fee and the payout currency arrive when Paddle completes the transaction, usually minutes later (until then they're estimates). Payouts come from payout reconciliation reports: Paddle creates payouts on the 1st and pays them by the 15th.

RevenueCat (revenue)

Connect it: RevenueCat (revenue)

About 3 minReported

Need

  • Key: Secret API key (V2)
  • Plan: Any RevenueCat project. One connection per project; each project has its own keys.
  • Permissions: Charts & metrics: Read only (charts_metrics:charts:read) Project configuration: Read only (project_configuration:projects:read, products:read) Customer information and everything else: No access

Create a secret API key (V2) in your RevenueCat project's settings with Charts & metrics and Project configuration set to Read only, and everything else No access. RevenueCat reports revenue per product and day after refunds, with its estimates of the stores' tax and commission. If Stripe or web purchases also go through RevenueCat, connect Stripe or RevenueCat for those sales, not both, or they count twice.

Steps not yet verified

Open RevenueCat (revenue)'s key page ↗ not yet verified

  1. In RevenueCat, open your project's settings → API keys and click + New secret API key.
  2. Name it Burnstack revenue and choose V2 as the version.
  3. Set Charts & metrics and Project configuration to Read only, and every other permission to No access.
  4. Click Generate, then copy the secret key (sk_…).
  5. Paste it into Burnstack under Connectors → Add revenue.

Paste it

In Burnstack: Connectors → Add revenue → RevenueCat → Add key → paste → Validate & save. The key goes straight into your computer's keychain. Revenue tracking needs the free beta license: Activate free on the Profit page.

If it fails

This is a public SDK key, which can't read revenue
Public keys (appl_…, goog_…) are for apps. Create a secret API key (V2) with the permissions listed.
RevenueCat API error 401
The key is a V1 key, was deleted or was mistyped. Create a new secret API key and choose V2.
RevenueCat API error 403 not yet verified
Set Charts & metrics and Project configuration to Read only on the key (edit it in the project's API keys).

Let your AI do the clicking not yet verified

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens RevenueCat (revenue)'s key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://app.revenuecat.com/ in my browser. Choose '+ New secret API key'. Enter 'Burnstack revenue' as the name and select V2 as the version. Set Charts & metrics and Project configuration to Read only and every other permission to No access. RevenueCat has no expiry setting for this secret API key, so skip that. Stop before clicking 'Generate' (the final button that creates the secret API key) and tell me it's ready. I'll click it, copy the secret API key and paste it into Burnstack myself. Don't copy, read or paste the secret API key, and don't grant broader access or change any other setting. If RevenueCat asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Reported: From RevenueCat's own sales data. Anything Burnstack has to estimate until RevenueCat settles it is marked provisional.
  • History: No documented limit; the first sync reads 400 days of the daily revenue chart (25 chart requests a minute).
  • Delay: Revenue appears as RevenueCat receives purchases; today's figures are incomplete and the last day is provisional. Tax and store commission are RevenueCat's estimates; App Store and Google Play settle them later.

Lemon Squeezy (revenue)

Connect it: Lemon Squeezy (revenue)

About 2 minFees estimated

Need

  • Key: API key
  • Plan: Any Lemon Squeezy store. A key sees every store of its user; use a live-mode key (test-mode keys return test orders).
  • Permissions: Orders, subscriptions and products: Read (Lemon Squeezy keys can't be limited; Burnstack only sends read requests)

Create an API key under Settings → API. Lemon Squeezy keys can't be limited to reading, so this one could also change your store; Burnstack only reads orders, subscriptions and products. Lemon Squeezy is the merchant of record and pays the tax on your sales. It doesn't report its fees, so Burnstack estimates them from its published pricing (5% + 50¢, +0.5% on subscriptions). Keys last a year.

Steps not yet verified

Open Lemon Squeezy (revenue)'s key page ↗

  1. In Lemon Squeezy, open Settings → API.
  2. Click the + button to create an API key and name it Burnstack revenue.
  3. Create it and copy the key (shown once).
  4. Paste it into Burnstack under Connectors → Add revenue.

Paste it

In Burnstack: Connectors → Add revenue → Lemon Squeezy → Add key → paste → Validate & save. The key goes straight into your computer's keychain. Revenue tracking needs the free beta license: Activate free on the Profit page.

If it fails

Lemon Squeezy API error 401: Unauthenticated
The key was deleted, mistyped or is over a year old. Create a new API key and use Replace key.
This Lemon Squeezy key can't see any store
Create the key while signed in as a user of the store.

Let your AI do the clicking not yet verified

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Lemon Squeezy (revenue)'s key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://app.lemonsqueezy.com/settings/api in my browser. Create a new API key and enter 'Burnstack revenue' as its name. Lemon Squeezy keys have no permission settings, so there is nothing else to choose. Lemon Squeezy has no expiry setting for this API key, so skip that. Stop before clicking 'Create' (the final button that creates the API key) and tell me it's ready. I'll click it, copy the API key and paste it into Burnstack myself. Don't copy, read or paste the API key, and don't grant broader access or change any other setting. If Lemon Squeezy asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Fees estimated: Sales and refunds as Lemon Squeezy reports them; the fees it doesn't report are estimated from its published pricing, so its days stay provisional.
  • History: No documented limit; the first sync covers 400 days. Each sync also reads 90 days before its window for refunds.
  • Delay: Sales appear when paid. Fees are estimated from published pricing (5% + 50¢, +0.5% on subscriptions), so Lemon Squeezy days stay provisional.

Polar (revenue)

Connect it: Polar (revenue)

About 2 minReported

Need

  • Key: Organization access token
  • Plan: Any Polar organization in production (sandbox tokens aren't supported).
  • Permissions: Orders: Read (orders:read) Refunds: Read (refunds:read) Organizations: Read (organizations:read) Products: Read (products:read), optional Every other scope (anything :write): not selected

Create an organization access token under Settings → Access Tokens with only the read scopes listed here and an expiration. Polar is the merchant of record: it pays the tax on your sales, which shows as its own step on the Profit page, and reports its fee on each order.

Steps not yet verified

Open Polar (revenue)'s key page ↗ not yet verified

  1. In Polar, open your organization's Settings → Access Tokens and click Create token.
  2. Name it Burnstack revenue and pick an expiration.
  3. Select only the read scopes orders:read, refunds:read, organizations:read and products:read.
  4. Create it and copy the token (polar_oat_…).
  5. Paste it into Burnstack under Connectors → Add revenue.

Paste it

In Burnstack: Connectors → Add revenue → Polar → Add key → paste → Validate & save. The key goes straight into your computer's keychain. Revenue tracking needs the free beta license: Activate free on the Profit page.

If it fails

Polar API error 401
The token expired, was revoked or is a sandbox token. Create a new production token and use Replace key.
Polar API error 403: Give the organization access token the refunds:read scope
Create a token that also has the scope named.

Let your AI do the clicking not yet verified

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Polar (revenue)'s key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://polar.sh/dashboard in my browser. Choose 'Create token' and enter 'Burnstack revenue' as the name. Select only the scopes orders:read, refunds:read, organizations:read and products:read, and no scope ending in :write. Set Expiration to 90 days (or the closest shorter option). Stop before clicking 'Create' (the final button that creates the token) and tell me it's ready. I'll click it, copy the token and paste it into Burnstack myself. Don't copy, read or paste the token, and don't grant broader access or change any other setting. If Polar asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Reported: From Polar's own sales data. Anything Burnstack has to estimate until Polar settles it is marked provisional.
  • History: No documented limit; the first sync covers 400 days.
  • Delay: Orders appear when paid, with Polar's fee and the tax it remits. Refunds count on the day they're made.

App Store (revenue)

Connect it: App Store (revenue)

About 5 minReported

Need

  • Key: Team API key (Issuer ID, Key ID, vendor number, .p8)
  • Plan: An Apple Developer Program membership with paid apps or in-app purchases, and an Admin to create the team key. Apple Pay is a payment method inside Stripe, Paddle and the like, not this; App Store is the store that pays app developers.
  • Permissions: Role: Finance (sales and trends and financial reports) Sales role: daily figures only, never settled Admin and every other role: not needed not yet verified

A team API key with the Finance role. Paste the Issuer ID, the Key ID and your vendor number, each on its own line, then the contents of the .p8 file; add a line "Commission: 15%" if you're in the App Store Small Business Program (otherwise Apple's 30% is assumed, 15% for subscriptions after a year). The private key stays on this computer and signs a short-lived token for each request. Daily figures are estimates until Apple's monthly financial report settles them. Apple Pay is a payment method that already flows through Stripe or Paddle; this is for apps and in-app purchases sold on the App Store.

Steps

Open App Store (revenue)'s key page ↗

  1. In App Store Connect, open Users and Access → Integrations → App Store Connect API → Team Keys.
  2. Click Generate API Key (or +), name it Burnstack revenue and choose the Finance role.
  3. Click Generate, then Download API Key (the .p8 file, available once) and note the Key ID and the Issuer ID above the list.
  4. Find your vendor number in Payments and Financial Reports (top left).
  5. In Burnstack, paste the Issuer ID, Key ID and vendor number on their own lines, then the .p8 file's contents.

Paste it

In Burnstack: Connectors → Add revenue → App Store → Add key → paste → Validate & save. The key goes straight into your computer's keychain. Revenue tracking needs the free beta license: Activate free on the Profit page.

If it fails

App Store Connect API error 401
The Issuer ID, Key ID or private key don't match, or the key was revoked. Copy them again from Users and Access → Integrations.
App Store Connect API error 403
The key's role can't read reports. Generate a team key with the Finance role.
App Store Connect API error 400 not yet verified
The vendor number is wrong. Copy it from Payments and Financial Reports.
The Issuer ID is missing
Paste the Issuer ID, the Key ID and the vendor number on their own lines above the private key.

Let your AI do the clicking

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens App Store (revenue)'s key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://appstoreconnect.apple.com/access/integrations/api in my browser. Make sure the Team Keys tab is selected and click 'Generate API Key' (or the + button). Enter 'Burnstack revenue' as the name and choose Finance as the access role, nothing broader. App Store Connect API keys have no expiry setting. App Store has no expiry setting for this private key, so skip that. Stop before clicking 'Generate' (the final button that creates the private key) and tell me it's ready. I'll click it, copy the private key and paste it into Burnstack myself. Don't copy, read or paste the private key, and don't grant broader access or change any other setting. After I've downloaded it, show me where the Issuer ID and the Key ID are on that page, and where the vendor number is under Payments and Financial Reports, without copying them. If App Store asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Reported: From App Store's own sales data. Anything Burnstack has to estimate until App Store settles it is marked provisional.
  • History: Daily sales reports go back 365 days, so the first sync covers a year; financial reports settle each fiscal month.
  • Delay: Daily reports appear the next day and are estimates (Apple's commission and the tax are estimated from the proceeds). They become final when the month's financial report is published, by the first Friday of the next fiscal month.

Google Play (revenue)

Connect it: Google Play (revenue)

About 10 minReported

Need

  • Key: Reports bucket and service account JSON key
  • Plan: A Google Play developer account with paid apps or in-app purchases; the Play Console owner or an admin invites the service account. Google Pay is a payment method inside Stripe and the like, not this; Google Play is the store that pays app developers.
  • Permissions: Play Console account permission: View financial data, orders and cancellation survey responses (global) Google Cloud IAM roles: none (Play Console grants the bucket access) OAuth scope requested: devstorage.read_only

A Google Cloud service account invited in Play Console with View financial data. Paste the reports bucket from Play Console (Download reports → Copy Cloud Storage URI, gs://pubsite_prod_rev_…) on the first line and the service account's JSON key file below it. Burnstack asks Google for read-only Cloud Storage access and reads the monthly report files. Estimated sales are provisional, with Google's fee estimated at 15% or 30%, until the month's earnings report replaces them. Google Pay is a payment method that already flows through Stripe and the like; this is for apps and in-app purchases sold on Google Play.

Steps not yet verified

Open Google Play (revenue)'s key page ↗

  1. In Google Cloud console, create a service account (no roles needed) and a JSON key for it under Keys → Add key.
  2. In Play Console, open Users and permissions → Invite new users and invite the service account's email.
  3. Under Account permissions, turn on only View financial data, orders and cancellation survey responses, then Invite user.
  4. In Play Console, open Download reports → Financial and click Copy Cloud Storage URI.
  5. In Burnstack, paste the URI (gs://pubsite_prod_rev_…) on the first line, then the JSON key file's contents.

Paste it

In Burnstack: Connectors → Add revenue → Google Play → Add key → paste → Validate & save. The key goes straight into your computer's keychain. Revenue tracking needs the free beta license: Activate free on the Profit page.

If it fails

Google Cloud Storage API error 403
The service account can't read the bucket yet. Give it View financial data in Play Console (Users and permissions); it can take up to a day to apply.
isn't a Play Console reports bucket
Copy the bucket from Play Console → Download reports → Copy Cloud Storage URI and paste it on the first line.
Google refused the service account key
The key was deleted or disabled. Create a new JSON key for the service account.

Let your AI do the clicking not yet verified

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Google Play (revenue)'s key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://play.google.com/console/developers in my browser. Choose 'Invite new users', enter the service account's email address (I'll tell you which), and under Account permissions turn on only 'View financial data, orders and cancellation survey responses'; leave every app permission and admin permission off. Google Play has no expiry setting for this invitation, so skip that. Stop before clicking 'Invite user' (the final button that creates the invitation) and tell me it's ready. I'll click it, copy the invitation and paste it into Burnstack myself. Don't copy, read or paste the invitation, and don't grant broader access or change any other setting. Then open Download reports → Financial and show me the Copy Cloud Storage URI button, without copying anything. If Google Play asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Reported: From Google Play's own sales data. Anything Burnstack has to estimate until Google Play settles it is marked provisional.
  • History: As far back as the monthly report files go; the first sync covers 400 days.
  • Delay: Estimated sales arrive within days and are estimates (Google's fee is estimated at 15% or 30%). The monthly earnings report, typically there by the 5th of the next month, replaces them with Google's actual fee and tax. not yet verified

PayPal (revenue)

Connect it: PayPal (revenue)

About 5 minReported

Need

  • Key: REST app client ID and secret
  • Plan: A PayPal Business account with access to the developer dashboard. Sandbox apps work too: add the word sandbox to what you paste.
  • Permissions: Feature: Transaction search (scope https://uri.paypal.com/services/reporting/search/read) Every other feature: off where PayPal allows

Create a REST app on developer.paypal.com (Apps & Credentials, Live) with the Transaction search feature, and paste its client ID and secret as CLIENT_ID:SECRET (add the word sandbox for a sandbox app). Burnstack only searches your transactions: sales, refunds, chargebacks, PayPal's fees and withdrawals to your bank.

Steps not yet verified

Open PayPal (revenue)'s key page ↗

  1. On developer.paypal.com, open Apps & Credentials and switch to Live.
  2. Click Create App, name it Burnstack revenue and create it as a Merchant app.
  3. In the app's Features, turn on Transaction search and turn off every feature PayPal lets you remove; save.
  4. Copy the Client ID and the Secret.
  5. Paste them into Burnstack as CLIENT_ID:SECRET under Connectors → Add revenue.

Paste it

In Burnstack: Connectors → Add revenue → PayPal → Add key → paste → Validate & save. The key goes straight into your computer's keychain. Revenue tracking needs the free beta license: Activate free on the Profit page.

If it fails

This PayPal app can't search transactions
Turn on Transaction search in the app's Features; it can take a few hours to apply.
PayPal API error 401: Client Authentication failed
The client ID or secret is wrong, or a sandbox app was pasted without the word sandbox.

Let your AI do the clicking not yet verified

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens PayPal (revenue)'s key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://developer.paypal.com/dashboard/applications/live in my browser. Switch to Live, choose 'Create App', enter 'Burnstack revenue' as the app name and choose Merchant as the type. PayPal has no expiry setting for this client secret, so skip that. Stop before clicking 'Create App' (the final button that creates the client secret) and tell me it's ready. I'll click it, copy the client secret and paste it into Burnstack myself. Don't copy, read or paste the client secret, and don't grant broader access or change any other setting. After the app is created, open its Features, turn on Transaction search and turn off every other feature PayPal lets you remove, then save. Don't copy the client ID or secret. If PayPal asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Reported: From PayPal's own sales data. Anything Burnstack has to estimate until PayPal settles it is marked provisional.
  • History: Three years (Transaction Search's limit); the first sync covers 400 days.
  • Delay: Transactions appear within three hours, with PayPal's fee.

Start watching back.

Five minutes to connect your first vendor. Free for Mac, forever, and every byte stays yours.