Google APIs
274 APIs7,055 Endpoints22 Categories
Categories
API Catalog(22 of 274)
Ad Exchange Buyer API II
The Ad Exchange Buyer API II lets Authorized Buyers programmatically manage their accounts on Google's Ad Exchange. It covers client and invitation management, real-time bidding configurations including pretargeting and creatives, auction packages, marketplace programmatic deals (proposals, products, deals, finalized deals), and bidder-level filtering and bid metric reports. Buyers and demand-side platforms use it to provision client buyers, run experiments, troubleshoot bid filtering, and negotiate deals with publishers without using the Authorized Buyers UI.
50 endpointsAd Experience Report API
The Ad Experience Report API exposes Google's findings on sites that show ads violating the Better Ads Standards — interruptions like full-page interstitials, auto-playing video with sound, and prestitial countdown ads. It returns the ad-experience status (Failing, Passing, or Not Reviewed) for a single site and a list of all sites currently failing the report. Publishers and ad-quality teams use it to monitor whether their domains are at risk of having Chrome filter ads on them.
2 endpointsAdMob API
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.
Connect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.