canonical: https://jentic.com/apis/googleapis.com/authorizedbuyersmarketplace

# Google Authorized Buyers Marketplace API

The Authorized Buyers Marketplace API lets authorized programmatic buyers discover publisher inventory, propose private deals, negotiate terms, and manage finalised deals at scale. It exposes operations to send RFPs to publishers, subscribe clients to auction packages, attach creatives to deals, and signal that a deal is ready to serve. Resources are scoped to a buyer account and the API is the integration surface between a DSP or trading desk and Google's Authorized Buyers programmatic marketplace. It does not deliver impressions or report on served traffic.

## For AI agents

Discover programmatic ad inventory, propose and negotiate private deals with publishers, and attach creatives in Google Authorized Buyers Marketplace.

## Scope

Does not deliver impressions, run real-time bidding, or report on served traffic - use for proposal, deal, client, and auction-package management in Authorized Buyers only.

## Capabilities

- Send RFPs to publishers via /v1/{+buyer}/proposals:sendRfp to initiate deal negotiation
- Subscribe and unsubscribe clients to auction packages with subscribeClients and unsubscribeClients
- Attach a creative to a deal with /v1/{+deal}:addCreative before serving
- Set a deal ready-to-serve via /v1/{+deal}:setReadyToServe to mark it live
- List proposals, deals, clients, and auction packages scoped to a buyer account
- Patch deal terms and proposal fields during negotiation to update price floors and targeting

## Use cases

### Programmatic Direct Deal Negotiation

Initiate, negotiate, and finalise private deals with publishers programmatically rather than by manual UI flows. The API supports sending an RFP, listing the publisher's response, patching deal terms, and ultimately marking the deal ready to serve. Suitable for trading desks that manage hundreds of deals and want them version-controlled in code.

Example prompt: POST an RFP payload to /v1/{buyer}/proposals:sendRfp with target inventory, dates, and price, then poll the proposal until the publisher responds.

### Auction Package Subscription Management for Agencies

Manage which client accounts under an agency buyer have access to which curated auction packages. The API supports listing available packages, subscribing a set of clients to a package, and unsubscribing them when the campaign ends. Keeps client access tightly scoped without manual provisioning.

Example prompt: POST a list of client resource names to /v1/{auctionPackage}:subscribeClients to grant them access to that package.

### Creative Trafficking and Deal Activation

Attach approved creatives to a finalised deal and then mark the deal ready to serve so it begins receiving impressions. The API exposes addCreative and setReadyToServe as discrete operations so trafficking and activation can be tracked and audited in a workflow tool.

Example prompt: POST the creative resource name to /v1/{deal}:addCreative, then POST to /v1/{deal}:setReadyToServe to activate.

### AI Agent for Deal Hygiene via Jentic

Use an AI agent to keep a buyer's pipeline clean by listing open proposals, flagging stalled negotiations, and following up with publishers via standardised RFP messages. Through Jentic the agent searches by intent, loads each operation's schema, and executes calls without managing OAuth refresh logic itself.

Example prompt: Use Jentic search for 'list authorized buyers proposals', filter results by lastUpdatedTime older than 14 days, and call sendRfp to nudge stalled deals.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/{+buyer}/proposals:sendRfp | Send a request-for-proposal to a publisher |
| POST | /v1/{+deal}:addCreative | Attach a creative to a deal |
| POST | /v1/{+deal}:setReadyToServe | Mark a deal ready to serve impressions |
| POST | /v1/{+auctionPackage}:subscribeClients | Subscribe a list of clients to an auction package |
| POST | /v1/{+auctionPackage}:unsubscribeClients | Unsubscribe clients from an auction package |
| GET | /v1/{+name} | Get a proposal, deal, client, or auction package by resource name |
| PATCH | /v1/{+name} | Update a proposal or deal during negotiation |

## Key resources

- **proposals** — RFP and deal negotiations between buyer and publisher
- **deals** — Finalised deals with addCreative and setReadyToServe operations
- **clients** — Agency client accounts that can be subscribed to auction packages
- **auctionPackages** — Curated inventory bundles offered by publishers
- **publisherProfiles** — Profile information on participating publishers

## Why Jentic

- **Setup:** Wiring the Authorized Buyers Marketplace API by hand means setting up Google OAuth2, scoping the buyer account, and refreshing access tokens for each proposal and deal call yourself. Through Jentic you install once, import the Authorized Buyers Marketplace API from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** This API puts the buyer, deal, and auction package in the URL path (/v1/{buyer}/proposals:sendRfp, /v1/{deal}:addCreative), so a rule can pin your agent to one buyer: it can send RFPs, add creatives, and subscribe clients for that buyer and nothing else. You choose the operations it may call, so actions like setting a deal ready to serve are not included unless you add them.
- **Credential handling:** Your Authorized Buyers OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send an RFP to a publisher' or 'add a creative to a deal', and Jentic returns the matching Marketplace operation with its input schema so the agent calls the right endpoint without navigating the Authorized Buyers reference.

## Related APIs

- **Real-time Bidding API** — Manages bidder configuration and creatives that serve via Authorized Buyers deals
- **Display & Video 360 API** — Buy-side platform for advertisers running campaigns rather than direct deals
- **Bid Manager API** — Reporting on bidding activity that complements deal negotiation

## FAQ

### What authentication does the Authorized Buyers Marketplace API use?

The API uses Google OAuth 2.0 with the authorized-buyers-marketplace scope. The OAuth client must be linked to an Authorized Buyers buyer account approved by Google. Through Jentic the OAuth credential is held in the encrypted vault and only short-lived access tokens reach the agent.

### Can I send RFPs to publishers through this API?

Yes. POST to /v1/{buyer}/proposals:sendRfp with the publisher reference, target inventory, flight dates, and pricing terms. The publisher then responds asynchronously and the proposal can be polled and patched until both sides agree.

### How do I attach a creative to a deal through Jentic?

Search Jentic for 'attach a creative to an Authorized Buyers deal'. Jentic returns the POST /v1/{deal}:addCreative operation with its schema; execute it with the deal name and creative resource name, then follow with setReadyToServe to activate.

### What are the rate limits for the Authorized Buyers Marketplace API?

Numeric limits are not declared in the OpenAPI spec; quotas are enforced per Google Cloud project on authorizedbuyersmarketplace.googleapis.com. Check the project quota dashboard before scheduling large list jobs across many buyer accounts.

### Does this API report on impressions or revenue?

No. This API covers deal negotiation, client subscriptions, and creative attachment only. Impression-level reporting lives in the Ad Manager API and the Authorized Buyers Real-Time Bidding APIs.

### Can I subscribe multiple agency clients to the same auction package?

Yes. POST /v1/{auctionPackage}:subscribeClients accepts a list of client resource names so an agency can grant access to many clients in a single call.

### Can I limit what my agent is allowed to do with the Authorized Buyers Marketplace API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API puts the buyer, deal, and auction package right in the URL path (/v1/{buyer}/proposals:sendRfp, /v1/{deal}:addCreative), so you can pin the agent to a single buyer account. You choose the exact operations it may call, for example letting it send RFPs, add creatives, and subscribe clients while omitting setReadyToServe so it can never mark a deal live on its own. The Google OAuth credential stays with your instance and is injected only when an allowed call runs, so the agent acts only within the scope you granted.