AdMob API

Name: AdMob API API
Brand: AdMob API
Availability: InStock

✓ Official Vendor SpecMarketingAdvertisingoauth26 EndpointsREST

For Agents

Read AdMob account, app, and ad-unit data and generate network or mediation reports so an agent can report on mobile ad earnings and fill rate without using the AdMob UI.

Quickstart

Get started with AdMob API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"generate an admob network report for the last 7 days"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AdMob API API.

List the AdMob accounts and publisher IDs the calling Google account has access to

Enumerate apps registered under an AdMob account, including app store identifiers

List ad units configured on each app, with their format and reward settings

Generate network reports across dimensions such as country, format, ad unit, and date

GET STARTED

Start building with AdMob API API

Explore with Jentic

View OpenAPI Spec

Use for: Get the AdMob account ID for my Google account, List all apps in an AdMob account, List all ad units for a specific AdMob app, Generate an AdMob network report for the last 30 days by country

Not supported: Does not handle creative trafficking, mediation group configuration changes, or in-app purchase data — use for reading AdMob account, app, ad-unit, and report data only.

The AdMob API lets mobile app publishers programmatically read account, app, ad unit, and reporting data from their AdMob account. It exposes endpoints to list AdMob accounts the caller has access to, enumerate apps and ad units under each account, and generate network and mediation reports against custom date ranges and dimensions. App publishers and analytics teams use it to feed AdMob earnings into BI dashboards, monitor ad-unit fill rate, and produce reconciliation reports without scraping the AdMob UI.

Use Cases

Patterns agents use AdMob API API for, with concrete tasks.

★ Mobile Earnings Dashboard

A mobile publisher pipes AdMob earnings into an internal BI dashboard alongside in-app purchase revenue. The networkReport:generate endpoint accepts a date range, dimensions (such as APP and COUNTRY), and metrics (estimated earnings, impressions, eCPM), returning streamed rows that the pipeline writes to a warehouse.

Generate a network report for accounts/pub-1234 covering the last 30 days, grouped by APP and DATE, with ESTIMATED_EARNINGS and IMPRESSIONS metrics, and write each row to BigQuery.

Ad Unit Inventory Sync

A mobile platform team syncs the catalogue of AdMob ad units into a configuration store so client SDKs can pick the right unit at runtime. Apps.list and adUnits.list under an account return the app and ad unit identifiers, which the team caches keyed by app store ID.

List apps under accounts/pub-1234 and, for each app, list its ad units, then upsert {appId, adUnitId, format} rows into the platform config store.

Mediation Performance Review

An ad-ops team reviews mediation performance every week to decide which networks to keep in the waterfall. The mediationReport:generate endpoint groups metrics by mediation group and ad source, producing the eCPM and match rate that drive the team's priority adjustments.

Generate a mediation report for accounts/pub-1234 covering last week, grouped by AD_SOURCE and MEDIATION_GROUP, sort by eCPM, and reply with the top 5 underperforming sources.

AI Agent Revenue Insights

An AI agent embedded in a mobile growth tool answers questions like 'which country drove the most AdMob revenue last week?' through Jentic. The agent calls networkReport:generate with the right dimensions, normalises the streamed response, and replies with a one-paragraph answer.

Given the question 'which country drove the most AdMob revenue last week', call networkReport:generate grouped by COUNTRY, sort rows by ESTIMATED_EARNINGS descending, and return the top country with its earnings figure.

Key Endpoints

6 endpoints — the admob api lets mobile app publishers programmatically read account, app, ad unit, and reporting data from their admob account.

METHOD

PATH

DESCRIPTION

GET

/v1/accounts

List AdMob accounts the caller can access

GET

/v1/{+parent}/apps

List apps under an AdMob account

GET

/v1/{+parent}/adUnits

List ad units under an AdMob account

POST

/v1/{+parent}/networkReport:generate

Generate a network report for an account

POST

/v1/{+parent}/mediationReport:generate

Generate a mediation report for an account

GET

/v1/accounts

List AdMob accounts the caller can access

GET

/v1/{+parent}/apps

List apps under an AdMob account

GET

/v1/{+parent}/adUnits

List ad units under an AdMob account

POST

/v1/{+parent}/networkReport:generate

Generate a network report for an account

POST

/v1/{+parent}/mediationReport:generate

Generate a mediation report for an account

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google OAuth 2.0 credentials are stored encrypted in the Jentic vault (MAXsystem) and exchanged for short-lived access tokens at request time. The agent never sees the refresh token directly.

Intent-based discovery

Agents search by intent (e.g., 'generate admob network report') and Jentic returns the matching networkReport:generate or mediationReport:generate operation with its input schema, so dimension and metric fields are pre-typed.

Time to first call

Direct integration: 1-2 days for OAuth setup, scope review, and report-streaming plumbing. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

AdSense Management API

Reporting and inventory API for AdSense web publishers

Choose AdSense for web inventory and AdMob for mobile app inventory — they share concepts but cover different publisher surfaces.

Complementary

DoubleClick Bid Manager API

Reporting on Display & Video 360 buying activity

Use Bid Manager for buy-side mobile reporting and AdMob for sell-side publisher reporting on the same app.

Complementary

Play Developer Reporting API

Read Play Console app reliability and engagement metrics

Pair Play Developer Reporting with AdMob to correlate app crash and engagement metrics with ad revenue.

FAQs

Specific to using AdMob API API through Jentic.

What authentication does the AdMob API use?

It uses Google OAuth 2.0 with the https://www.googleapis.com/auth/admob.readonly or admob.report scope. The calling Google account must have access to the target AdMob 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 AdMob earnings through the API?

Yes. POST /v1/{parent=accounts/*}/networkReport:generate with a dateRange of 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 AdMob API?

The default quota is 60 queries per minute per project. Report generation calls are streamed and count as a single request regardless of the number of returned rows, so batching dimensions tightly keeps quota usage low. Long-running reports must be consumed within the response timeout or restarted.

How do I list ad units for an AdMob app through Jentic?

Run jentic search 'list admob ad units', load the accounts.adUnits.list operation, and execute it with parent set to accounts/{publisherId}. The agent receives a typed list of ad units with adUnitId, format, and adFormat fields, ready to feed into a downstream config sync.

Is the AdMob API free?

Yes. The AdMob API has no per-call fee and is available to anyone with an AdMob publisher account. Earnings reported by the API reflect the standard AdMob revenue share.