Pull every number in Pulse into your reports and your AI tools.
/api/v1/search-console?from=2026-08-01&to=2026-08-31
/api/v1/search-console?from=2026-08-01&to=2026-08-31
Connect your dashboards, your data warehouse or your AI assistant to the same data you see in Pulse. Each API key has the same access as the person it belongs to.
Read your search, site, content and competitor data.
The API covers rankings, share of voice, Search Console, GA4, Business Profile, pages, backlinks, content and ideas across 21 read endpoints. The docs endpoint defines every call and field, so an analyst can start pulling data the day the key is created.
/rankingsPositions by keyword and day/share-of-voiceGoogle and AI answers by topic/search-consoleClicks, impressions, queries/ga4Sessions and conversions/backlinksReferring domains and links/auditsSite Health scores and findings/sqlRead-only SQL over all of itEvery call, with its fields, from the docs endpoint.
Connect Claude, ChatGPT, Gemini or Copilot to live Pulse data.
Pulse runs an MCP server, the Model Context Protocol that assistants use to reach outside data, so the same tools are open to Claude from Anthropic, ChatGPT from OpenAI, Gemini from Google and Copilot from Microsoft. Ask a question of your Pulse data from any of them and the answer comes from the same numbers the app shows, read live, with the connection acting as the person who set it up.
Ask in the Agent →ClaudeChatGPTGeminiCopilotWhich topics did we lose share on in August, and which pages carry them?
Read share of voiceAug 1 to Aug 31Read rankings243 keywordsRead Search Console31 daysThe share of voice it reads is the number on your Visibility page.
Give each person a key with the same access they already have.
Every key is created for a named user and carries that user’s permissions, so the API can never return more than the person behind it could see on screen. Keys read and never write. The SQL endpoint is checked for writes before a statement runs and stopped if it runs too long.
Every key reads. SQL is checked, and stopped if it runs long.
Everything you see in Pulse, from rankings to backlinks to content.
Accounts, rankings, Search Console, GA4, Business Profile insights and reviews, Google Ads, pages and page keywords, share of voice, audits, backlinks, schema, content and the content pipeline, competitors, media coverage and keyword plans. If the app reads it, the API returns it.
Strategy & Reporting, run by our team →
Search Console
GA4
Business ProfileYour data, wherever your team already works.
Pull it, query it, or connect your AI to it.
Straight answers about the API.
What can we pull through the API?
The same data as the app: accounts, rankings, Search Console, GA4, Business Profile insights and reviews, Google Ads, pages and page keywords, share of voice, audits, backlinks, schema, content and the content pipeline, competitors, media coverage and keyword plans. Twenty-one read endpoints plus a read-only SQL endpoint.
Is it read-only?
Yes. Every key reads and never writes. The SQL endpoint is checked for writes before a statement runs and stopped if it runs too long.
Who can create a key?
Our team creates a key for a named user on your team. The key carries that user’s permissions, so it can never return more than they could see on screen.
Can we connect our own AI?
Yes. Pulse runs an MCP server, so Claude, ChatGPT, Gemini, Copilot and any other assistant that speaks the Model Context Protocol can ask questions of your Pulse data from the workspace your team already uses. The connection acts as the person who set it up.
Is there documentation?
Yes. A docs endpoint describes every call, its parameters and the fields it returns, and it stays current with the API.
Are there limits?
Yes, on request volume and on how long a SQL statement may run. Ask us about the limits for your plan before you build on it.
Put your Pulse data where your team already looks.
Send us your site. We’ll connect your data, create a key for your analyst, and walk you through the first call.