# Superwall: Subscription Infrastructure for iOS, Android, and Web

Subscription infrastructure — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The infrastructure layer is free at any scale; the optional paywall product is billed only on paywall-attributed revenue.

## Pricing

- **Infrastructure: free at any scale, every plan.** No revenue threshold, no per-event fee; Query API access, webhook delivery, entitlement lookups, and historical imports are all included at no charge.
- **Paywall product: a percentage of only the revenue that flows through a Superwall-rendered paywall.** Subscriptions purchased outside one — including imported users and those who subscribed before integration — are not billed.

Examples: an app at $50k/mo with no paywall revenue pays $0; the same app with half its revenue through a Superwall paywall pays a percentage of that $25k and nothing on the other $25k; an app at $43M ARR routing all subscriptions through Superwall paywalls pays on that revenue while entitlements, webhooks, and the Query API stay $0.

## Scale

$1.5B+ annual subscription revenue across 10,000+ apps. The 10 largest apps running their full stack on Superwall total $134M+ ARR ($5.7M–$43.7M each). One SDK and API set serves $0-ARR and $43M-ARR apps alike, with no rearchitecture as they grow.

## Infrastructure capabilities

- **Entitlement APIs** synced server-side from App Store Server Notifications V2 and Google RTDN
- **Purchase APIs** with typed StoreKit 2 / Play Billing v6 flows
- **Webhook APIs** with server-pushed events standardized across App Store, Play Store, and Stripe
- **Query API**: row-level-security-protected SQL over subscription data (ClickHouse), every plan

Handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, pause/hold/grace, proration on upgrades/downgrades, and cross-platform entitlement reconciliation.

## Migration

Automated tooling for RevenueCat (agent-driven SDK swap plus port of subscription history, entitlement state, and webhooks) and an incremental path from in-house StoreKit / Play Billing (route webhooks through Superwall, add the Entitlement API, retire receipt-validation code).

## Paywall product (optional, separately billable)

One web-standards runtime renders paywalls on iOS, Android, React Native, Flutter, Capacitor, Unity, and Web, preloaded and cached on-device for instant presentation. Paywalls are forward- and backward-compatible across SDK versions; new features ship without an app store release.

## Architecture

Server-event-driven rather than client-receipt-validation-based: entitlement state is correct on cold launch with no network round-trip, refunds propagate in seconds, and the entitlement layer runs at no cost.

## Docs

* Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall
* Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse
* Webhooks: https://superwall.com/docs/integrations/webhooks
* Pricing: https://superwall.com/pricing

# Superwall API

Call the Superwall REST API with an organization API key, the same API the MCP, CLI, and Superwall AI use.

The Superwall API is the REST API behind the dashboard, the [Superwall MCP](/docs/agents/mcp), the [Superwall CLI](/docs/agents/cli), and [Superwall AI](/docs/agents/superwall-ai). Use it directly when you're building your own integration or script.

If you're working with an AI agent, you usually don't need to call the API yourself. The [plugin](/docs/agents/plugins), MCP, and CLI already use it with your account's permissions.

## Reference

The full reference, with every endpoint and its parameters, is at [api.superwall.com/docs](https://api.superwall.com/docs). The OpenAPI spec is at [api.superwall.com/openapi.json](https://api.superwall.com/openapi.json). You can give either one to an agent so it can write requests for you.

The base URL is `https://api.superwall.com`, and endpoints are versioned under `/v2`, for example `/v2/projects` and `/v2/products`.

## Authentication

Requests use an organization API key as a bearer token:

```bash
curl https://api.superwall.com/v2/projects \
  -H "Authorization: Bearer $SUPERWALL_API_KEY"
```

Create keys in the dashboard under **Settings › API Keys**. Each key has scopes, which control the resources it can read or write, and project access, which controls the projects it can reach. See [API key access](/docs/dashboard/dashboard-settings/overview-settings-access-controls#api-key-access).

## From the CLI

The CLI can make authenticated API calls using your `superwall login` session, so you don't need a key:

```bash
superwall get /v2/products
superwall post /v2/products -d project_id=<project-id> -d identifier=pro_monthly -d name="Pro Monthly" -d 'price[amount]:=9.99' -d 'price[currency]=USD'
```

See [Call the API](/docs/agents/cli#call-the-api) in the CLI guide.

## Analytics queries

To run SQL against your analytics data, use [`superwall query`](/docs/agents/cli#query-your-analytics-data) or the [ClickHouse query API](/docs/dashboard/guides/query-clickhouse).