Connect Webflow with a site API token
Connects one Webflow site using a site API token, created in the
site's Site settings > Apps & integrations > API access with Sites
read-only and CMS read and write access. Zernio checks the token's
scopes, reads its site, and stores the token encrypted. Webflow is a
connect-only blog platform: each CMS collection with a rich text field
is a blog in the Blogs API (/v1/accounts/{accountId}/blogs); it does
not support social posts, inbox, analytics or ads. Publishing an
article needs a site that has been published once. Reconnecting the
same site and profile updates the connection in place.
API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.connect.connectWebflowWithSiteToken({ body: { profileId: 'profile_abc123', siteToken: 'tok_abc123', },});console.log(data);{ "account": { "_id": "string", "platform": "webflow", "username": "string", "displayName": "string", "profileId": "string" }}Connect self-hosted WordPress with an application password
Connects one self-hosted WordPress site using a WordPress username and application password. `siteUrl` must use HTTPS and may include the path where WordPress is installed. Zernio discovers the REST API, verifies the credentials and required post/media/taxonomy capabilities, then stores the password encrypted. Create an application password in the WordPress user's profile; do not send the user's login password. Reconnecting the same site and profile updates the connection in place.
Connect a Whop account
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.