Skip to main content

Use cases

  1. Create a checkout configuration
  2. Onboard sub-merchants
  3. Verify your platform account
  4. Programmatically pay out users
  5. Generate payout onboarding links for your sub-merchants
Before you begin, follow the Quickstart to create an API key.

Troubleshoot API requests

Debug authentication failures, permission errors, retryable responses, and sandbox/production mismatches.

API keys

Use Account API keys when you only want to fetch data or perform actions for your own Account and connected accounts.
  1. Follow the Quickstart API key steps and open Account API Keys.
  2. Select Create in the Account API Keys section.
  3. Give your API key a name, such as Data pipeline or GHL Integration.
  4. Select a role or a custom set of permissions. You can update the key and add permissions later.
  5. Create the API key, and copy it from the modal.
Use app API keys when you are building an app and need to access data on companies that have installed your app.
  1. Open your dashboard and choose the business that owns the app.
  2. Open DeveloperApps.
  3. Select Create app and give the app a name, or select an existing app.
  4. On App details, find Get startedSet up your local environment.
  5. Use the copy button in Copy these environment variables to copy the real WHOP_API_KEY, then store it securely. You will need it to make API calls on behalf of the app.
This WHOP_API_KEY is the app’s API credential. It’s different from the runtime secrets managed by whop apps secrets, which are arbitrary key-value environment bindings for your hosted code.
Use OAuth tokens when you want users to sign in with their Whop account and grant your app permission to act on their behalf. Unlike API keys which use your app’s permissions, OAuth tokens are scoped to what each individual user can access.Common use cases:
  • “Sign in with Whop” authentication
  • Accessing a user’s memberships, purchases, or profile
  • Performing actions as a specific user (not as your app)
OAuth tokens are obtained through the OAuth 2.1 + PKCE flow:
  1. Redirect users to Whop’s authorization page
  2. User logs in and approves your requested scopes
  3. Exchange the authorization code for access and refresh tokens
  4. Use the access token as your API key in SDK calls or the Authorization header
See the OAuth guide for full implementation details.

Making API calls

The public API is available at https://api.whop.com/api/v1. Use curl to test the API by fetching your public user profile data:
To make authenticated requests you need to include your API key in the Authorization header using the Bearer scheme:

SDK reference

MCP

You can also access the API through the Whop Model Context Protocol server at https://mcp.whop.com/mcp (Cursor) or https://mcp.whop.com/sse (Claude). Learn more here