List Google Analytics properties for a pending connect
For headless flows. When the connect started with redirect_url=...?headless=true and the Google
account can read several GA4 properties, Zernio redirects to your redirect_url with
step=select_property, profileId, platform=googleanalytics and a pendingDataToken. Call this
to list the properties and show your own picker, then call
POST /v1/connect/googleanalytics/select-property. Listing does not consume the token. A headless
token passes through your own URLs, so it is honored only together with your API key (or connect
token) for the same profile. It expires after one hour.
API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Query Parameters
Token from the headless redirect.
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.listGoogleAnalyticsProperties({ query: { pendingDataToken: 'tok_abc123', },});console.log(data);{ "properties": [ { "propertyId": "string", "displayName": "string", "accountId": "string", "accountName": "string" } ]}Get Wix site install URL
Returns the Wix installer link for the Zernio app. The user picks one of their Wix sites there and approves the app; Wix then returns the browser to Zernio's internal callback, which connects that site and redirects to `redirect_url` (or the dashboard when omitted). Wix is a connect-only blog platform: the connected account powers the Blogs API (`/v1/accounts/{accountId}/blogs`) and does not support social posts, inbox, analytics or ads. The site needs the Wix Blog app. Access tokens renew by themselves; removing the Zernio app from the site in Wix disconnects the account.
Connect the chosen Google Analytics property
For headless flows. Connects the property the user picked as a `googleanalytics` account and returns where to send the user next: your `redirect_url` with `connected=googleanalytics`, `profileId`, `accountId` and `username`, or an `error` when the connect was refused (for example a billing block). Consumes the `pendingDataToken`; a refused or failed attempt leaves it usable for a retry. Send your API key (or connect token) for the same profile with a headless token.