Two ways to build
Build Whop into your product
Your app, your domain, your users. Whop handles payments, payouts, identity, and money movement behind the scenes through the API and SDKs. Start with an API key.
Build an app that runs inside Whop
Ship into Whop’s marketplace, where thousands of businesses install apps. Auth, views, and distribution are built in. Start with the CLI, not an API key.
Everything on the platform
Each row is a capability. Each column is how deep you integrate: call the API directly, drop in a prebuilt element, send users to a hosted surface, or listen for webhooks.
Everything runs against the sandbox before it touches real money. Webhooks fire for the events that matter, like
payment.succeeded and membership.activated, so your server always knows what happened.
Start with what you came for
You sell a subscription or a one-time product
Checkout links or embedded checkout. First payment in under an hour.
You owe money to people who aren't you
Send payouts, embed the payout portal, top up balances.
You take a cut of what other people sell
Enroll connected accounts, collect on their behalf, pay them out.
You want distribution, not just infrastructure
Ship an app to businesses already on Whop. Auth and views included.
Your product needs people talking to each other
Chat, DMs, and forums, embedded in your product.
You just want to read the reference
The versioned Current API, endpoint by endpoint.
Make your first call
Start the quickstart
Create an API key and make your first authenticated call in about five minutes. Everything above starts here.