Google AdSense Management API
Browse all Google APIs38
AI ReadinessNon-Ready (F)38/100
Official vendor OpenAPI document · agent-readyMarketingAdvertisingoauth225 EndpointsREST
For Agents
Read AdSense accounts, ad clients, ad units, channels, payments, and alerts and generate earnings reports so an agent can monitor web ad revenue without using the AdSense UI.
Use for: List AdSense ad clients on my account, Generate an AdSense earnings report for the last 30 days by site, Get yesterday's AdSense estimated earnings for a specific ad unit, List all AdSense alerts on my account
Not supported: Does not handle ad creative review, ad unit code generation, or content-policy enforcement - use for reading AdSense account, inventory, payment, and report data only.
The AdSense Management API lets web publishers programmatically read their AdSense inventory and earnings. It exposes operations to enumerate accounts, ad clients, ad units, custom channels, URL channels, sites, payments, alerts, and saved reports, and to generate ad-hoc earnings and performance reports against custom date ranges, dimensions, and metrics. Publishers and analytics teams use it to feed AdSense data into BI dashboards, monitor channel performance, and produce reconciliation reports without scraping the AdSense UI.
Install Jentic One Beta
Connect the AdSense Management API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AdSense Management API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fadsense" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fadsense" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AdSense Management API.
List AdSense accounts the calling Google account has access to and read account state
Enumerate ad clients (AdSense for Content, AdSense for Search) and ad units under each account
List custom and URL channels used to slice reporting by site section or content topic
Generate earnings and performance reports across configurable dimensions and metrics, with CSV export
Read payments history and current unpaid balance for an AdSense account
List sites associated with an account and their auto-ads readiness
Surface AdSense alerts (policy issues, payment holds) so they can be routed to ops channels
Use Cases
Patterns agents use AdSense Management API for, with concrete tasks.
★ Publisher Earnings Dashboard
A web publisher pipes AdSense earnings into a BI dashboard alongside affiliate and subscription revenue. The reports:generate endpoint accepts a date range, dimensions (such as DOMAIN and DATE) and metrics (estimated earnings, page views, RPM), returning rows that the pipeline writes to a warehouse. The reports:generateCsv variant streams large date ranges directly as CSV.
Generate a report for accounts/pub-1234 covering the last 30 days, grouped by DOMAIN and DATE, with ESTIMATED_EARNINGS and PAGE_VIEWS metrics, and write each row to BigQuery.
Channel Performance Analysis
An ad-ops team reviews custom channel performance to decide which content topics deserve more inventory. The customchannels.list endpoint enumerates channels per ad client, and the reports:generate call with dimension=CUSTOM_CHANNEL_NAME returns per-channel earnings and click-through rate.
List custom channels under accounts/pub-1234/adclients/ca-pub-X, then generate a report grouped by CUSTOM_CHANNEL_NAME for last week and reply with the top 5 channels by RPM.
Payment Reconciliation
A finance team reconciles AdSense payments against earnings statements every month. Payments.list and accounts.get return the current unpaid balance and historical payments, which the team compares to the same period's earnings report to spot delayed or split payments.
List payments under accounts/pub-1234 for the last 12 months, sum the amounts, compare to total ESTIMATED_EARNINGS in the same period, and emit any delta over 1%.
AI Agent Revenue Q&A
An AI agent embedded in a publisher growth tool answers free-form questions like 'how much did Site A earn yesterday?' through Jentic. The agent picks the right reports:generate dimensions and metrics, executes the call, and replies with a one-paragraph answer.
Given the question 'how much did exampleblog.com earn yesterday', call reports:generate filtered to DOMAIN=exampleblog.com with metric ESTIMATED_EARNINGS for yesterday, and reply with the value in USD.
Key Endpoints
25 endpoints — the adsense management api lets web publishers programmatically read their adsense inventory and earnings.
METHOD
PATH
DESCRIPTION
GET
/v2/accounts
List AdSense accounts the caller can access
GET
/v2/{+name}
Get a single AdSense resource (account, ad client, ad unit, channel, site)
POST
/v2/{+account}/reports:generate
Generate an AdSense earnings or performance report as JSON
POST
/v2/{+account}/reports:generateCsv
Generate an AdSense report as CSV
GET
/v2/{+name}/adBlockingRecoveryTag
Get the ad-blocking-recovery tag for an account
GET
/v2/accounts
List AdSense accounts the caller can access
GET
/v2/{+name}
Get a single AdSense resource (account, ad client, ad unit, channel, site)
POST
/v2/{+account}/reports:generate
Generate an AdSense earnings or performance report as JSON
POST
/v2/{+account}/reports:generateCsv
Generate an AdSense report as CSV
GET
/v2/{+name}/adBlockingRecoveryTag
Get the ad-blocking-recovery tag for an account
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
AdSense Management API
- Non-Ready (F)38/100
58
Foundational Compliance56
Developer Experience & Jentic Compatibility17
AI-Readiness & Agent Experience94
Agent Usability63
Security64
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
58
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C+Signals: 4
71%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
17
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
66%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
64
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
64%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the AdSense Management API by hand means setting up Google OAuth 2.0, minting short-lived access tokens from a refresh token, and pointing read and report calls at the adsense.googleapis.com host. Through Jentic you install once, import the AdSense Management API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
AdSense puts the account resource in the URL path (/v2/{+account}/reports:generate, /v2/{+name}), so a rule can pin your agent to one AdSense account: it can read that account's inventory and payments and nothing else. You choose the operations it may call, so report generation or CSV export is not included unless you add them.
Credential isolation
Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and exchanged for short-lived access tokens at execution time. The refresh token never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'generate an AdSense earnings report' or 'list AdSense accounts', and Jentic returns the matching AdSense operation with its input schema, so the dimension and metric fields are pre-typed and the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AdSense Management API through Jentic.
What authentication does the AdSense Management API use?
It uses Google OAuth 2.0 with the https://www.googleapis.com/auth/adsense.readonly or adsense scope. The calling Google account must own or have delegated access to the target AdSense publisher account. Jentic stores the OAuth credential in its encrypted vault and exchanges it for short-lived access tokens at request time.
Can I get yesterday's AdSense earnings through the API?
Yes. POST /v2/{account=accounts/*}/reports:generate with dateRange.startDate and endDate set to yesterday, dimensions=[DATE], and metrics=[ESTIMATED_EARNINGS] returns the previous day's earnings as soon as Google has finalised the day's data, typically within a few hours after midnight Pacific Time.
What are the rate limits for the AdSense Management API?
The default quota is 10,000 queries per day per project, with bursts limited to a few queries per second. Report generation calls return paginated responses - clients must follow nextPageToken to retrieve full result sets, and CSV streaming requests should set Accept: text/csv to skip JSON parsing.
How do I list ad clients on an account through Jentic?
Run jentic search 'list adsense ad clients', load the accounts.adclients.list operation, and execute it with parent set to accounts/{publisherId}. The agent receives a typed list of ad clients with name, productCode (AFC, AFS), and reportingDimensionId.
Is the AdSense Management API free?
Yes. The API has no per-call fee and is available to anyone with an AdSense publisher account. Earnings reported by the API reflect the standard AdSense revenue share.
Can I limit what my agent is allowed to do with the AdSense Management API?
Yes. Because you run Jentic One yourself, your own rules decide which AdSense operations and credentials the agent may use. Since AdSense puts the account in the URL path (/v2/{+account}/reports:generate and /v2/{+name}), you can pin the agent to a single AdSense account so it reads only that account's inventory, payments, and alerts. You also pick the exact operations it may call, so report generation and CSV export stay off unless you add reports:generate and reports:generateCsv.
GET STARTED