Get a phone handoff
Where a connect started with handoff=true on GET /v1/connect/{platform} stands: waiting until the QR code is scanned, opened once the phone opened it, then connected with the new accounts or failed with the error the flow ended on (the same error codes as the redirect flow). expired when nobody opened the QR code within its 30 minutes. Poll it every 2 to 5 seconds while your QR code is shown, and stop once it is connected, failed or expired. Readable for 60 minutes after it was created, then 404, as is a handoff created by another workspace.
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Path Parameters
handoff.id from the connect response.
uuidResponse 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.getConnectHandoff({ path: { handoffId: '00000000-0000-0000-0000-000000000000', },});console.log(data);{ "id": "79c6dbf2-97ba-4f34-b615-5bf9435526db", "status": "connected", "platform": "instagram", "accounts": [ { "id": "6ab0c2f1e4d5a6b7c8d9e0f1", "profileId": "69b0a1b2c3d4e5f6a7b8c9d0", "username": "acme" } ], "error": null}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.
Get the saved welcome screen
The workspace's saved welcome screen settings, shared by the whole team. With `showByDefault` on, every `GET /v1/connect/{platform}` made with your API key shows the welcome screen before the platform's authorization screen, without `welcome=true` or any branding parameter. Connects started from the Zernio dashboard always show it, with this branding when saved.