Connect

Connect a Whop account

Changed on

Connect a Whop account with an Account API key from the Whop dashboard (Developer > API keys). The key only has to be able to read its own account: Zernio calls GET /accounts/me once to learn the account id (biz_...) and name, then stores the key.

What the connection unlocks today is the Whop Pixel through the tracking-tags API: the account id is the pixel, so GET /v1/accounts/{accountId}/tracking-tags lists it and POST .../tracking-tags/{biz_...}/install puts it on a Shopify store or WordPress site. Whop campaigns are not managed through Zernio. One Whop account per profile.

post/v1/connect/whop-ads/credentials

Request

  • Base URL: https://zernio.com/api
  • URL: https://zernio.com/api/v1/connect/whop-ads/credentials
  • Auth: HTTP bearer

Request body

apiKeystring required

Account API key from the Whop dashboard.

profileIdstring required

Your Zernio profile ID

statestring

Optional state passthrough for the connect flow.

redirect_urlstring uri

Optional URL to redirect to after successful connection, echoed back as redirectUrl.

Response

Whop account connected

accountIdstring

The Zernio account id (platform whopads) to use as {accountId} on the tracking-tags routes.

whopAccountIdstring

The Whop account id (biz_...), which is also the tracking tag id.

accountNamestring
redirectUrlstring

Changes