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.
- On success: your
redirect_urlwithconnected=googleanalytics,profileId,accountIdandusername. - When the connect was refused (for example a billing block): an
error.
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.
Authentication
One of these
API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
One of these
Short-lived connect token for API users during OAuth flows. Automatically generated when initiating OAuth without a browser session. Valid for 15 minutes. Connect tokens are scoped to the intended profile and platform and are accepted only by connection-flow endpoints that explicitly list this security scheme.
Body
application/jsonWhat every request needs
Token from the headless redirect.
A propertyId from the properties list.
Responses
Success· the request worked
Errors· the request failed
List Google Analytics properties for a pending connect
For headless flows: lists the GA4 properties of a pending Google Analytics connect, so you can show your own picker. ### Flow 1. The connect started with `redirect_url=...?headless=true`, and the Google account can read several GA4 properties. 2. Zernio redirects to your `redirect_url` with `step=select_property`, `profileId`, `platform=googleanalytics` and a `pendingDataToken`. 3. Call this to list the properties and show your own picker. 4. Call `POST /v1/connect/googleanalytics/select-property`. ### Token - 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.
List Google Business Profile locations
For headless flows. Returns the list of Google Business Profile locations the user can manage. Use pendingDataToken (from the OAuth callback redirect) to list locations without consuming the token, so it remains available for select-location. Use X-Connect-Token header if connecting via API key.