Google does not document a public API for searching the Ads Transparency Center. Google’s documented Google Ads API is a separate product for programmatic work with Google Ads accounts. A third-party article reports that the public Transparency Center website uses an internal search RPC, but that observation is not a Google-supported API and may stop working or change without notice.
What the Ads Transparency Center does
Google describes the Ads Transparency Center as a place to “Find active ads published through Google.” Its public interface lets visitors search by advertiser name or website and use filters and contextual controls. It is a search interface for viewing ads, not documentation for a developer service.
As an Amazon Associate I earn from qualifying purchases.
The interface also states that ads shown before September 4, 2023 will not appear in search results when a platform filter is selected. That is a specific limitation of the public search interface, not a general statement about the age or completeness of every result.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Is there an official API for Transparency Center searches?
The available official Google documentation describes the Google Ads API, which developers use to interact programmatically with Google Ads accounts. Google documents access through REST or gRPC and recommends its client libraries where possible. That documentation does not establish a search API for the Ads Transparency Center.
#1 Best Overall
Google’s API call structure guide describes OAuth bearer tokens and developer-token requirements for Google Ads API requests. Those requirements apply to that documented API; they should not be confused with the access behavior reported for the Transparency Center website.
A Google Ads API Forum Advisor answered a related question on July 15, 2024, saying, “I have checked and found that there is no corresponding API for this yet.” This is a dated response from that discussion, not confirmation of current availability. For the present distinction, the key point is that Google’s cited developer documentation covers the Google Ads API, not a documented Transparency Center search endpoint.
Rank #2
What the third-party reverse-engineering report says
A third-party article, “Reverse-engineering the Google Ads Transparency Center API”, published approximately two weeks before October 4, 2026, reports that the public site uses an internal RPC called SearchService/SearchCreatives. The reported endpoint is https://adstransparency.google.com/anji/_/rpc/SearchService/SearchCreatives. The author describes a POST request with an application/x-www-form-urlencoded body containing URL-encoded f.req data and numeric protobuf-JSON fields.
The report also says its observed requests could be made anonymously. That is the author’s observation, not a Google access guarantee. The available material does not establish a complete schema, confirm that every field is understood, or independently verify that the described request still works. The endpoint, request format, and behavior may change at any time.
How the official API and reported RPC differ
| Question | Google Ads API | Reported Transparency Center RPC |
|---|---|---|
| Status | Officially documented by Google. | Internal endpoint reported by a third party; not documented in the cited Google sources. |
| Purpose | Programmatic interaction with Google Ads accounts. | Reportedly used by the public website to search ad creatives. |
| Access model | Google documents OAuth and developer-token request requirements. | The third-party author reports anonymous requests; this is unverified and could change. |
| Stability | Google provides documentation and official client libraries; check current versions and requirements before implementing. | No support or compatibility guarantee is established; the endpoint and numeric field mapping may change. |
| Policy scope | Google’s developer policies address use of Google Ads programmatic capabilities, including certain proxy arrangements. | The cited policy does not specifically adjudicate this internal RPC or every form of public-site research. |
What this means if you need ad-search data
If your goal is to look up ads, use the public Transparency Center interface and its available search and filter controls. If your goal is to manage or query your own Google Ads account programmatically, consult the documented Google Ads API and its authentication requirements. These solve different problems; the account API should not be treated as a substitute for Transparency Center search.
If you are evaluating the reported RPC for research or a prototype, treat it as an unstable observation rather than a production integration. Do not build a service around it on the assumption that Google will preserve its URL, request format, anonymous access, or results. Avoid exposing secrets, personal information, or session-specific tokens if examining browser traffic.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Policy considerations and limits
Google Ads Developer Policies prohibit certain third-party hosted interfaces or proxy services that solely replicate, wrap, or re-expose Google Ads programmatic capabilities as an intermediate layer. The policy excerpt distinguishes these arrangements from open-source tools users download and connect with their own credentials. This is relevant to services built around Google Ads API capabilities; it does not, by itself, determine the status of the Transparency Center’s reported internal RPC or every kind of public-site research.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
