Introducing IndexNow push + index-loss alerts: the coverage that matters

API reference

Everything indexsubmit tracks — index coverage, URL status, GA4 traffic and usage — is available over a public REST API and an MCP server for AI agents.

Quickstart by task

Four things you'll do first — each in one call.

Get the scored coverage — indexed, not indexed, errored — for a whole site, with a 30-day trend.

curl https://app.indexsubmit.com/api/v1/sites/{siteId}/coverage \
  -H "Authorization: Bearer isx_..."

Authentication

Every request carries a Bearer API key (isx_…). Keys are created in the dashboard under Settings → Developer; the full key is shown exactly once. Scopes: read for all data endpoints, submit for IndexNow submissions. Keys can be restricted to specific sites.

curl https://app.indexsubmit.com/api/v1/sites \
  -H "Authorization: Bearer isx_..."

Endpoints

  • sites — site inventory with index-coverage summaries and 90-day daily series
  • submissions — IndexNow push jobs (idempotent, async status polling)
  • ga4 — traffic × index-state correlation (recoverable views)
  • usage — per-key usage counters and plan limits

Rate limits

120 requests/min per key and 300 requests/min per user. 429 responses carry a Retry-After header. Submission batches are capped at 1,000 URLs.

Tenant isolation & permissions

A key only ever sees data from its own account. The site allowlist applies to reads and submissions alike; resources outside it return 404. Full request/response schemas, including error shapes, are in the interactive reference.