What is APIs-Google?
APIs-Google delivers push notifications from Google APIs to application endpoints. Despite this directory entry's search-crawler category, the documented request is a webhook delivery, not a page-discovery crawl. Developers use the notifications so an application can react to changes without repeatedly polling Google's servers.
Google requires a developer to prove control of a domain before registering a URL on that domain as a notification destination. Once configured, APIs-Google sends the message to the registered HTTPS endpoint. This explains why a domain administrator may see the user agent even though no public page was submitted for indexing.
The official APIs-Google documentation says each notification is an HTTPS POST and the receiving site needs a valid SSL certificate. Temporary delivery failures cause retries with exponential backoff, potentially continuing for several days. A broken route can therefore produce recurring requests without any crawl of neighboring URLs.
Robots support is specific. APIs-Google does not use rules written for Googlebot, and Google's special-crawler table says it ignores the global * group. It does honor rules addressed directly to APIs-Google, which is why this file records respectsRobotsTxt: true. A wildcard-only policy does not control this sender.
There is no search-index or AI-training consequence to document for these webhook requests. Blocking APIs-Google interrupts delivery of configured Google API notifications. It does not opt a site out of Google Search, AI Overviews, Gemini grounding, or model training.
The full recorded header is APIs-Google (+https://developers.google.com/webmasters/APIs-Google.html). Cloudflare's bot directory marks followsRobotsTxt as false, which differs from Google's documented support for a dedicated group and may reflect the ignored wildcard. No Web Bot Auth signature URL or verified IP flag is present, so do not authenticate a notification from the user-agent string alone.
