Whop
Manage Whop memberships, products, plans, payments, promo codes and webhooks.
About
Whop ships in the w6w first-party pack. It declares 35 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.whop- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Commerce & Payments · Finance & Accounting
Overview
Whop is a creator-commerce platform: sellers list Products, price them with Plans, and buyers hold Memberships that track billing state (active, trialing, past_due, canceled, …) and access. This app covers the operational path around that model — read and manage Memberships (list, retrieve, update metadata, cancel, pause, resume, extend with free days), read and manage the Products and Plans that back them, read and refund Payments, run Promo Codes end to end, and manage the Webhook endpoints that notify a workflow of what changed instead of polling for it.
Whop’s REST API is versioned by date: every request this app sends pins a confirmed Api-Version-Date, because a request without one silently falls back to the pre-2025 API shape — different field names (company_id instead of account_id), different parameter conventions — for every native resource the versioning changelog has since migrated.
Members and Users cover the buyer side: a Member is one buyer’s relationship with an account regardless of how many Memberships they hold, and a User is the underlying Whop identity, with an access check for gating content by product or experience.
Build with Whop
Three routes to the same 35 actions. The Workflow tab is generated from Whop's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Members
member-list List an account's members, one row per buyer regardless of membership count.
Cancel Membership
membership-cancel Cancel a membership, immediately or at the end of the current billing period.
Extend Membership
membership-extend Add free days to a membership, extending its period, expiration, or trial.
List Memberships
membership-list List memberships, optionally narrowed by account, user, product, plan or status.
Pause Membership
membership-pause Pause a membership's recurring payment collection while keeping access.
Resume Membership
membership-resume Resume a previously paused membership's recurring payment collection.
Update Membership
membership-update Merge metadata key-value pairs into a membership, or toggle its scheduled cancel-at-period-end.
Create Plan
plan-create Create a pricing plan for a product: billing interval, price and availability.
Delete Product
product-delete Delete a product. Fails if it has any memberships, entries, reviews or invoices.
Update Product
product-update Update an existing product's title, description, visibility or metadata.
Activate Promo Code
promo-code-activate Turn an inactive promo code back on so it can be redeemed at checkout.
Create Promo Code
promo-code-create Create a promo code (percentage or flat-amount discount) for an account.
Deactivate Promo Code
promo-code-deactivate Turn off an active promo code so it can no longer be redeemed at checkout.
Check User Access
user-check-access Check whether a user has access to an account, product, or experience.
Create Webhook
webhook-create Create a webhook endpoint that receives event notifications via HTTP POST. The response includes a signing secret — treat it as sensitive.
Update Webhook
webhook-update Update a webhook's URL, subscribed events, pinned payload version, or enabled state.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Whop's real ids.
{
"manifestVersion": "2",
"name": "whop-example",
"steps": [
{
"id": "member-get",
"uses": {
"app": "io.w6w.whop",
"action": "member-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"memberId": "<memberId>"
}
}
]
}Here are some of the things you can do
-
Get Member
readmember-get -
List Members
searchmember-list -
Extend Membership
performmembership-extend -
Get Membership
readmembership-get -
List Memberships
searchmembership-list
+30 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Whop, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Whop. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "member-get",
payload: {
memberId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action member-get --payload '{"memberId":"<value>"}'Give an AI agent Whop — without giving it Whop's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.whop#member-get",
"input": {
"memberId": "<memberId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Whop connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Whop's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Whop itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Whop declares its own checks, so its health is a property of the app rather than something the host guesses at.
Whop platform status
Component status from status.whop.com (Website, Android App, iOS App). None of these components is the REST API specifically, so the page-level roll-up is what this check trusts, matching how a Statuspage-shaped source is read across this pack.