Learn how to build and run your SaaS on Whop
User
table to include the whop_user_id
and whop_username
columns.
Column | Type | Description |
---|---|---|
whop_user_id | string | Unique identifier for the user provided by Whop. |
whop_username | string | The user’s Whop username, helpful for display and logging. |
access.checkIfUserHasAccessToAccessPass
method (shown in Step 6) by passing the whop_user_id
and the relevant access pass (product) ID to determine whether the user should be allowed to access your software.
If you would prefer to not have manage your own user table or even a database, consider building a Whop app here.
plan_XXXXXXXXX
with your actual plan ID from the dashboard.checkoutUrl
it returns (as shown in Step 6).201
. This means that the license key is valid and can be used to access the product. Internally, the API sets the metadata of the license key that was passed in the API call.
400
is returned. This means that the license key is not valid and cannot be used to access the product.
Below is example metadata that would return this error.
Client-side