Reverse AdSense API: Publisher ID & Domain Lookup
Start with a domain to find available AdSense publisher IDs, then use one ID to discover associated domains. Treat the connections as research leads, not as proof of a common owner or private revenue.
Domain to publisher IDs · Publisher ID to domains
https://api.goanyapi.com/api/v1/adsenseRun a request to see the visual result
The response is organized into metrics, lists and tables that match the JSON on the right.
Run a request to see the response here
Fill in the demo parameters to preview an example response for free. Sign in to send live requests with your own parameters.
Read a publisher lookup response
Begin with a domain or publisher ID. The example starts from a single domain.
GET https://api.goanyapi.com/api/v1/adsense?domain=example.com
Authorization: Bearer YOUR_API_KEYThe available publisher IDs depend on the queried domain. This is an example request, not a captured response.
Key response paths
data.query- The normalized domain or pubId selected for this request.
data.publisherIds- Available publisher IDs from domain lookup; present only for that mode.
data.domains- Available associated domains from pubId reverse lookup; present only for that mode.
data.costCredits- Credits deducted for this request under the current configuration.
What the data can tell you
Domain to publisher IDs · Publisher ID to domains
Start with a domain
Enter a single hostname to inspect available publisher IDs associated with that website. The response gives you an identifier to investigate further; it does not reveal the publisher account owner or its private AdSense reports.
Reverse a publisher ID
Submit one pubId in the documented pub- followed by digits format to retrieve available associated domains. This is a separate request from the domain lookup, so keep the original ID and query conditions together.
Review connections carefully
Compare associated sites with public website evidence before drawing conclusions. A shared publisher ID can guide a research workflow, but it does not establish legal ownership, ad earnings or a business relationship.
From a question to a useful result
A practical workflow using the available data.
Check a known website
Start with an exact domain such as example.com and inspect the returned publisher IDs. If no ID is available, record the empty result rather than guessing an ID from an unrelated source.
Explore an association
Select one returned pubId and make a separate reverse lookup to view associated domains. Save the ID with the resulting list so you can explain why each site entered the review.
Validate the relationship
Review the sites and independent public evidence before reporting a relationship. Use Traffic or Ads Transparency only for their own supported questions; do not present cross-API signals as ownership proof.
Reverse AdSense Lookup API FAQ
Questions about fit, interpretation and integration.
Query the publisher ID with pubId to retrieve available associated domains. You can first query a known domain to look for publisher IDs.
No. Treat the connection as an association to investigate, not proof of identity or ownership.
No. It does not provide private earnings, clicks, account reports or advertising performance metrics.
Use the domain lookup first. If a publisher ID is returned, make a separate reverse lookup for that ID; each request has its own billing.
No. The public request accepts exactly one mode: a single domain or one pubId. For a domain-to-ID-to-domains investigation, make two separate calls and apply the current configured rate to each successful request. Automating a list of domains requires your own loop and request handling.
Successful valid requests use the current configured credit rate shown in the Tester and Docs. Invalid or failed requests do not consume credits; do not assume that a successful empty result is free.
Call the REST endpoint from Python or Node.js with a GoAnyAPI key, selecting either domain or pubId. For an AI assistant, connect GoAnyAPI MCP and confirm the AdSense tool is available before asking it to call the API. A two-step reverse lookup, storage and interpretation remain your own workflow.
Continue the site investigation
Use related GoAnyAPI pages for distinct research questions.