Connecting your providers

How connections work

• API keys, not OAuth. You create a key in your provider's dashboard and paste it into Metricneed.
• Read-only where possible. Metricneed only ever reads your data — we recommend read-only or restricted keys when your provider supports them.
• Validated live. Every key is checked against the provider before it's saved, so a wrong key fails immediately instead of silently.
• Encrypted at rest. Keys are stored with AES-256-GCM and used only server-side, never exposed to the browser. See Security & privacy.

Live vs Test mode

When you add a connection you pick a Mode. Use Live for your real revenue and Test (or Sandbox) to try things out with test data. The key you paste must belong to the environment you selected — the exact rule differs per provider and is spelled out on each provider's page.

Real-time updates (Pro)

On the Pro plan, Metricneed registers webhooks so new sales, subscriptions and refunds appear seconds after they happen, backed by a daily reconciliation sync. This is automatic for Stripe, Polar and Lemon Squeezy; Creem and RevenueCat need a one-minute manual step; Gumroad has no webhook API, so it stays current through the periodic sync. More in Syncing your data.

Choose a provider

Pick your provider for step-by-step setup:

• Creem — Creem dashboard → Developers. Validated before saving; stored encrypted.
• Stripe — Stripe Dashboard → Developers → API keys → Secret key. Validated before saving; stored encrypted.
• Polar — Polar → Settings → Developers → Organization Access Token. Validated before saving; stored encrypted.
• Lemon Squeezy — Lemon Squeezy → Settings → API → create an API key. Validated before saving; stored encrypted.
• RevenueCat — RevenueCat → Project settings → API keys → new V2 secret key (read access). Needs the Project ID below too. Validated before saving; stored encrypted.
• Gumroad — Gumroad → Settings → Advanced → Applications → generate an access token. Validated before saving; stored encrypted.