canonical: https://jentic.com/apis/googleapis.com/real-time-bidding # Google Real-time Bidding API 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. ## For AI agents Manage bidder endpoints, creatives, pretargeting configs, and user lists for Google's Authorized Buyers RTB integration. ## Scope 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. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **buyers** — Buyer accounts including remarketing tag retrieval and user lists - **bidders** — Bidder configurations with activate, suspend, open, and close operations - **creatives** — Creative resources including create, list, get, and watch for review status - **pretargetingConfigs** — Pretargeting filters that scope which inventory a bidder receives - **userLists** — Audience and remarketing user lists attached to a buyer ## Why Jentic - **Setup:** Wiring the Real-time Bidding API by hand means configuring Google OAuth 2.0 with the realtime-bidding scope, refreshing scoped access tokens, and tracking bidder, buyer, and creative resource names across the control-plane calls on realtimebidding.googleapis.com. Through Jentic you install once, import the Real-time Bidding API from the API Directory, store the OAuth credential once, and your agent calls it. - **Permission scoping:** This API puts the bidder, buyer, and creative in the URL path (/v1/{+name} and /v1/{+parent}/creatives), so a rule can pin your agent to one buyer or bidder account: it can list and update within that scope and nothing else. You choose the operations it may call, so state-changing ones like suspending a bidder are not included unless you add them. - **Credential handling:** Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and a scoped access token is injected at execution time. The credential never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'submit a creative' or 'update a pretargeting config', and Jentic returns the matching Real-time Bidding operation with its input schema so the agent calls the right endpoint without reading the Authorized Buyers documentation. ## Related APIs - **Ad Exchange Buyer II API** — Earlier-generation Authorized Buyers control plane that overlaps with Real-time Bidding - **Authorized Buyers Marketplace API** — Manages programmatic deals and proposals between buyers and publishers - **Display & Video 360 API** — Buy-side platform for managing display and video campaigns - **DoubleClick Bid Manager API** — Reporting and query API for DV360 campaigns ## FAQ ### 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. ### Can I limit what my agent is allowed to do with the Real-time Bidding API? Yes. Because your Jentic One instance is self-hosted, your own rules decide which operations and credentials the agent may use. Since this API puts the buyer, bidder, and creative in the URL path (/v1/{+name} and /v1/{+parent}/creatives), you can pin the agent to a single buyer or bidder account so it lists and updates only within that scope. You also choose which operations it may call, so state-changing ones like suspending a bidder are excluded unless you explicitly allow them.