Skip to main content
Whop has deprecated API v2 (https://api.whop.com/api/v2 and https://api.whop.com/v2). This page maps each v2 route to its replacement in the Current API at https://api.whop.com/api/v1 and lists what behaves differently.

Find your v2 calls

Every v2 response carries two headers: Log responses that include Deprecation to find every v2 call your integration still makes.

Switch to the Current API

1

Keep your API key

The Current API uses the same account API keys. If a request returns 403, the key is missing the permission that endpoint needs. Add it in Developer → API keys.
2

Install the SDK and pin a version

The official SDKs call the Current API and send the API version they were built against.
If you call the API without an SDK, send Api-Version-Date on every request. API versions explains pinning.
3

Replace each route

Use the tables below, then remove the v2 base URL from your code.

Route map

Memberships and licenses

Members and customers

Payments and checkout

Products and plans

Plans are now called variants. Variant IDs keep the plan_ prefix, so stored IDs still work.

Account, experiences, reviews, and webhooks

What changed

Partial updates

v2 updated a resource with POST /resource/{id}. The Current API uses PATCH /resource/{id} and changes only the fields you send.

Pagination

v2 paged with page and per and returned pagination.current_page and pagination.total_page. Current API lists return a data array and a page_info object. Pass first to set the page size and after with the previous page_info.end_cursor to get the next page. Stop when page_info.has_next_page is false. The SDKs page for you.

License keys

v2 validate_license checked a key and bound it to a machine in one call. In the Current API, your server retrieves the membership by license key, checks its status, and writes a hardware ID to metadata the first time someone uses the key. The SaaS guide has the full example. Keep these calls on your server. Your account API key can change every membership in your business, so never ship it inside downloadable software.

Webhooks

Webhooks created through v2 keep sending v2-format payloads. To receive the current format, create a new webhook from the dashboard or with POST /webhooks, move your handler to it, then delete the v2 webhook. Webhooks covers signature checks and event types.

Next steps

API versions

Pin a version so later changes never break your integration.

Webhooks

Verify signatures and handle the current event format.

Manage memberships

Cancel, pause, extend, and update memberships.

SaaS

Gate a web app or downloadable software with the Current API.