Integrations, API access and data exports
Choose an integration by the job it does. A search-data connection, an export and a webhook telling your team about a change are different data flows. Each connected site still needs its own authorization, and an integration does not add to a plan’s allowance.
Connect your data to a site
Section titled “Connect your data to a site”| Need | Guide | What it gives the loop |
|---|---|---|
| Your buyers’ real searches | Search Console | Buyer searches join your topics as private questions, deleted if you disconnect (privacy); the uploaded AI report becomes an outcome on Results and calibrates demand |
| Visits from AI assistants | Google Analytics | Sessions and key events AI assistants sent, an outcome on Results |
| What crawlers actually did | Crawler traffic | The day an engine’s crawler fetched a changed page, which dates verdicts; assistant fetches, an outcome |
| When something shipped | CMS and deploy webhooks | Audit findings marked implemented, and a change run to check them |
Move work into your team’s process
Section titled “Move work into your team’s process”- Linear, Jira, GitHub and Asana: hand a play and its evidence to the people doing the work.
- Claude and ChatGPT (MCP): ask an assistant about your workspace.
- Alerts: tell the team about access changes, severe findings and engine changes.
- Zapier, Make and n8n: events as triggers and the API as actions.
- Webhook reference: event payloads and signature verification.
A change notification is not a shipped play. A play is shipped when its acceptance check passes, and whether it worked is its verdict.
Export to dashboards or your own pipeline
Section titled “Export to dashboards or your own pipeline”The Looker Studio guide describes the connector and its fields. It reads a JSON export that a BI tool or a script can read directly:
GET /api/export/visibility.json?siteId=&from=&to=&others=
Create an API key with Export scope and the smallest site list it needs. Keep the key server-side in your pipeline or connector configuration, never in public page code or an openly shared spreadsheet.
For a warehouse, load the JSON export through your own pipeline. You own the loading schedule, table schema, retries and permissions. Keep the counts behind each share, so a grouped share can be calculated from totals rather than as an average of percentages.
API and terminal use
Section titled “API and terminal use”The API reference and the API-key guide cover authentication, scopes, site restrictions, rate limits and pagination. The API, MCP and hand-offs come with Growth and the plans above it. The command-line client is provided on request.
When a request fails, read the status and the error. Check the key’s expiry, scope and site restrictions before retrying. Runs also need a verified site and the allowance; an Export key cannot start a run.
Access and client reporting
Section titled “Access and client reporting”Team roles and site access control members separately from API keys. White-label branding neither grants nor restricts access. For client-only access, use the client role or site limits, then check with that member’s view.
For an agency, combine the monthly audit workflow with white-label reports. Keep the observation dates, the definitions and the evidence even when the report carries your own name.