Four APIs, One Umbrella: What “the GSC API” Actually Refers To

When an SEO or developer says “the GSC API,” they mean the Search Analytics API — the interface that returns queries, clicks, impressions, CTR, and position data. Under the Google Search Console umbrella, however, there are four distinct programmatic interfaces, plus a fifth data-access path (BigQuery bulk export) that operates on a different model entirely. Each has its own endpoint, quota, authentication requirement, and appropriate use case. Treating them as interchangeable is the first mistake; assuming the Indexing API indexes general pages on demand is the second.

The four APIs are the Search Analytics API (performance data: queries, clicks, impressions, position), the URL Inspection API (index status for one URL per call), the Sitemaps API (programmatic sitemap registration and management), and the Indexing API (officially supported only for pages with JobPosting or BroadcastEvent structured data). The BigQuery bulk export, announced February 21, 2023, is not a call-based API — it is a scheduled daily export configured in the GSC UI that writes all performance data to three BigQuery tables with no per-pull row cap.

New to Search Console? Start with What is Google Search Console before diving into the API layer. For the broader SEO measurement stack, the GSC API fits alongside GA4 behavioral data and other instrumentation tools.

Search Analytics API: Getting Past the 1,000-Row Cap

The GSC Performance report caps at 1,000 rows in the UI. The Search Analytics API raises that ceiling to 25,000 rows per request, queryable by date, country, device, and search type. For most sites, a complete daily pull stays within the 25,000-row single-request ceiling. For larger sites, use the startRow parameter to paginate: set "rowLimit": 25000 and increment startRow by 25,000 per page. The total ceiling is 50,000 rows per search type per site per day. Source: Google Search Console API Usage Limits; Search Console API — Getting All Your Performance Data.

Two data constraints apply to the API exactly as they apply in the UI. The 16-month retention window: the API surfaces no data older than 16 months, and data beyond that point is permanently deleted — no request structure retrieves it. Anonymized queries: rare queries that Google withholds for privacy do not appear in API results. For sites with a high proportion of long-tail queries, the anonymized bucket represents a meaningful share of total query volume. BigQuery bulk export also excludes them, flagging affected rows with is_anonymized_query = true and a null query field.

MB Adv Agency runs weekly rolling API pulls for client sites rather than on-demand UI exports — the only way to build consistent historical datasets before data ages out of the 16-month window. Once data is dropped, no API call retrieves it.

Key Takeaways

• There is no single “GSC API” — there are four: Search Analytics API (25,000 rows/request, 50,000/day), URL Inspection API (2,000 QPD per property), Sitemaps API (submit, list, get, delete), and Indexing API (JobPosting and BroadcastEvent only).
• The Indexing API does not index general pages. Google’s official documentation limits it to JobPosting and BroadcastEvent pages. Using it on blog posts or product pages is not a supported use case and carries no documented guarantee.
• The 16-month retention window applies to the Search Analytics API, not just the UI. Data older than 16 months is permanently deleted. BigQuery bulk export is the only mechanism for accumulating performance data beyond that window.
• The URL Inspection API’s 2,000 QPD limit is intentional — it is designed for targeted URL inspection, not bulk crawling. At 2,000 QPD, a 200,000-URL site takes 100 days to inspect every URL once.

API Capability Reference: What Each API Returns and Its Hard Limits

Data output, key quota, and authentication requirement for each interface. All APIs are free to use. Sources: Google Search Console API Usage Limits; URL Inspection API launch, January 2022; Indexing API Quickstart, April 2026; BigQuery Bulk Export, February 2023; GSC API Pricing.

The URL Inspection API (launched January 2022) returns the same data as the GSC UI’s URL Inspection tool, one URL per call. For index coverage states, see Index Coverage & Indexing. For sitemap context, see Sitemaps & URL Inspection. For teams managing GSC tracking setup alongside Google Tag Manager, the API data fits naturally into the same measurement stack.

Use-Case to API Mapping: Which API to Reach For

The table below maps common automation use cases to the correct GSC API or method. The “Not via Indexing API” row for general page indexing is intentional — it directly addresses the most common API misuse pattern this pillar exists to correct.

The Sitemaps API is narrow but concrete: the list endpoint lets a script verify every expected child sitemap is registered and flag missing entries — useful for large sitemap indexes. For how GSC processes submitted sitemaps, see Sitemaps & URL Inspection.

Authentication: One Divergence That Matters

Three of the four GSC APIs use standard OAuth 2.0 — either a user-consent flow or a service account — with the webmasters or webmasters.readonly scope. The Indexing API diverges: it requires a service account, not a user-consent flow, and a different scope. The service account must be granted delegated owner access to the GSC property before any API call succeeds. Sources: Search Console API — Authorize Requests; Indexing API — Authorize Requests.

This distinction matters in practice: a developer cannot reuse the OAuth client-ID credential flow from the Search Analytics or URL Inspection API for the Indexing API. Service account setup requires Google Cloud Console access, a JSON key file, and delegated owner status on the GSC property — not just editor or viewer access.

Data and methodology: Search volume figures from Ahrefs, June 2026 (operator-supplied). API quotas (25,000 rows/request; 50,000/day; 2,000 URL Inspection QPD; 200 Indexing API publish/day) verified against developers.google.com/webmaster-tools/limits and individual API documentation pages. Indexing API scope (JobPosting + BroadcastEvent only) from developers.google.com/search/apis/indexing-api/v3/quickstart (last updated April 2026). BigQuery export facts from developers.google.com/search/blog/2023/02/bulk-data-export and support.google.com/webmasters/answer/12918484. No MB Adv client metrics cited — agency attributions are qualitative observations only. Reviewed by MB Adv Agency, June 2026.