Google Real-time Bidding API
Browse all Google APIs✓ Official Vendor SpecMarketingAdvertisingoauth228 EndpointsREST
For Agents
Manage bidder endpoints, creatives, pretargeting configs, and user lists for Google's Authorized Buyers RTB integration.
Use for: I need to register a new creative with Google Authorized Buyers for review, Suspend a bidder configuration during a maintenance window, List all creatives that are currently disapproved for our buyer account, Update a pretargeting configuration to exclude a sensitive vertical
Not supported: Does not handle live bid request and response traffic, campaign budget management, or DSP-side campaign creation — use for Authorized Buyers RTB control-plane configuration only.
The Google Real-time Bidding API lets bidders and buyers manage their RTB integration with Google's Authorized Buyers exchange. It exposes operations to manage bidder endpoints, creatives, pretargeting configurations, user lists, and the publisher and creative review workflows that gate eligibility to bid. The API is the control plane for an RTB integration — bidding traffic itself flows over a separate OpenRTB or Google protocol bidder endpoint.
Install Jentic One Beta
Connect the Real-time Bidding API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Real-time Bidding 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://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.
Capabilities
What an agent can do with Real-time Bidding API.
Manage bidder configurations including the bidder endpoint and remarketing tag
Create, update, and watch creatives so they can be reviewed and approved for bidding
Configure pretargeting filters that scope which inventory a bidder receives
Manage user lists used for remarketing and audience targeting
Activate, suspend, open, or close bidder and buyer resources to control bidding eligibility
Retrieve creative review status and remarketing tag snippets for buyers
Use Cases
Patterns agents use Real-time Bidding API for, with concrete tasks.
★ Creative Management and Review
Bidders submit creatives to Google Authorized Buyers for review and must track approval status before the creative is eligible to serve. The Real-time Bidding API exposes create, list, get, and watch operations on creatives so the review pipeline can be automated end to end.
Create a creative under buyers/{accountId} with the HTML snippet and declared advertiser, then call watch to receive status updates until the creative is approved.
Pretargeting and Inventory Filtering
Bidders use pretargeting configurations to scope which inventory they receive bid requests for, reducing wasted compute on impressions they would never bid on. The API lets buyers manage these configurations programmatically and activate or suspend them around campaigns.
Update a pretargeting configuration to exclude geo:RU and content_label_excluded:G_CONTROVERSIAL_RELIGIOUS and call the activate operation.
Audience and Remarketing Lists
User lists power audience targeting and remarketing on the bidder side. The API exposes list management and remarketing tag retrieval so audience operations and tag deployment can be wired into the same automation pipeline that runs campaigns.
Retrieve the remarketing tag snippet via getRemarketingTag, then create a user list for site visitors and reference it in pretargeting.
Agent-Driven RTB Operations
An ad ops agent uses Jentic to perform RTB control-plane work — submitting creatives, toggling bidder state, and tweaking pretargeting filters — in response to campaign briefs or alerts, replacing manual console work for routine operations.
Search Jentic for submit a creative for review, load the schema for buyers.creatives create, and execute it with the creative payload from the campaign brief.
Key Endpoints
28 endpoints — the google real-time bidding api lets bidders and buyers manage their rtb integration with google's authorized buyers exchange.
METHOD
PATH
DESCRIPTION
GET
/v1/bidders
List bidder accounts
GET
/v1/buyers
List buyer accounts
POST
/v1/{+name}:activate
Activate a bidder or pretargeting config
POST
/v1/{+name}:suspend
Suspend a bidder or pretargeting config
POST
/v1/{+name}:getRemarketingTag
Retrieve the remarketing tag snippet for a buyer
POST
/v1/{+parent}/creatives:watch
Watch creatives for review status changes
GET
/v1/bidders
List bidder accounts
GET
/v1/buyers
List buyer accounts
POST
/v1/{+name}:activate
Activate a bidder or pretargeting config
POST
/v1/{+name}:suspend
Suspend a bidder or pretargeting config
POST
/v1/{+name}:getRemarketingTag
Retrieve the remarketing tag snippet for a buyer
POST
/v1/{+parent}/creatives:watch
Watch creatives for review status changes
Why 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. Scoped access tokens with the realtime-bidding scope are issued per call so the OAuth client secret never enters the agent, and IAM permissions on the buyer or bidder account determine what the agent can do.
Intent-based discovery
Agents search Jentic by intent (submit a creative, suspend a bidder, update a pretargeting config) and Jentic returns the matching Real-time Bidding operation with its input schema, replacing the need to read Authorized Buyers documentation per call.
Time to first call
Direct integration takes 3-7 days because Authorized Buyers onboarding, creative payload modelling, and pretargeting semantics each carry their own learning curve. Through Jentic: under 1 hour for individual operations once the buyer account is onboarded.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Real-time Bidding API through Jentic.
What authentication does the Real-time Bidding API use?
The API uses Google OAuth 2.0 with the realtime-bidding scope, sent as a Bearer token. Through Jentic the OAuth credentials are stored in the vault and short-lived access tokens are minted per call so the refresh token never enters the agent.
Does this API receive bid requests or send bids?
No, this is the control-plane API for managing bidder configuration, creatives, pretargeting, and user lists. Live bid requests and responses flow over a separate OpenRTB or Google protocol bidder endpoint that you operate.
What are the rate limits for the Real-time Bidding API?
Per-project quotas are documented in the Authorized Buyers documentation and are intended for control-plane volumes rather than per-impression traffic. Heavy creative submission workflows should batch and back off based on quota errors.
How do I submit a creative through Jentic?
Search Jentic for submit a creative to authorized buyers, load the schema for the buyers.creatives.create operation which maps to POST /v1/{+parent}/creatives, and execute it with the creative metadata. Then call watch to receive review status updates.
Is the Real-time Bidding API free?
The control-plane API itself is free, but actual ad serving on Authorized Buyers carries the standard transaction and auction fees documented by Google. Pricing for inventory and auction mechanics is unrelated to the API call volume.
How do I suspend a bidder configuration?
Call POST /v1/{+name}:suspend on the bidder resource to stop the bidder from receiving bid requests, then POST /v1/{+name}:activate when you want it back online. The suspend and close operations are useful during maintenance or while debugging integration issues.
GET STARTED