Automate Google Ad Exchange Buyer II
HumDay reads Google Ad Exchange Buyer II’s own published API description and derives 50 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Google Ad Exchange Buyer II is
Accesses the latest features for managing Authorized Buyers accounts, Real-Time Bidding configurations and auction metrics, and Marketplace programmatic deals.
API host: adexchangebuyer.googleapis.com
What HumDay can do in Google Ad Exchange Buyer II
22 documented operations change something in Google Ad Exchange Buyer II.
- POSTCreate a new note and attach it to the proposal.
/v2beta1/accounts/{accountId}/proposals/{proposalId}:addNote - POSTCreates a new client buyer.
/v2beta1/accounts/{accountId}/clients - POSTCreates and sends out an email invitation to access an Ad Exchange client buyer account.
/v2beta1/accounts/{accountId}/clients/{clientAccountId}/invitations - POSTCreates the specified filter set for the account with the given account ID.
/v2beta1/{ownerName}/filterSets - DELETEDeletes the requested filter set from the account with the given account ID.
/v2beta1/{name} - POSTCreates a creative.
/v2beta1/accounts/{accountId}/creatives - POSTCreate the given proposal.
/v2beta1/accounts/{accountId}/proposals - PUTUpdates an existing client user.
/v2beta1/accounts/{accountId}/clients/{clientAccountId}/users/{userId} - POSTAssociate an existing deal with a creative.
/v2beta1/accounts/{accountId}/creatives/{creativeId}/dealAssociations:add - PUTUpdates a creative.
/v2beta1/accounts/{accountId}/creatives/{creativeId} - PUTUpdate the given proposal at the client known revision number.
/v2beta1/accounts/{accountId}/proposals/{proposalId} - PUTUpdates an existing client buyer.
/v2beta1/accounts/{accountId}/clients/{clientAccountId} - POSTWatches a creative. Will result in push notifications being sent to the topic when the creative changes status.
/v2beta1/accounts/{accountId}/creatives/{creativeId}:watch - POSTUpdate the given proposal to pause serving.
/v2beta1/accounts/{accountId}/proposals/{proposalId}:pause - POSTMark the proposal as accepted at the given revision number.
/v2beta1/accounts/{accountId}/proposals/{proposalId}:accept - POSTUpdate the given proposal to resume serving.
/v2beta1/accounts/{accountId}/proposals/{proposalId}:resume - POSTStops watching a creative.
/v2beta1/accounts/{accountId}/creatives/{creativeId}:stopWatching - POSTYou can opt-in to manually update proposals to indicate that setup is complete.
/v2beta1/accounts/{accountId}/proposals/{proposalId}:completeSetup - POSTUpdate given deals to pause serving.
/v2beta1/accounts/{accountId}/finalizedProposals/{proposalId}:pause - POSTUpdate given deals to resume serving.
/v2beta1/accounts/{accountId}/finalizedProposals/{proposalId}:resume - POSTCancel an ongoing negotiation on a proposal.
/v2beta1/accounts/{accountId}/proposals/{proposalId}:cancelNegotiation - POSTRemove the association between a deal and a creative.
/v2beta1/accounts/{accountId}/creatives/{creativeId}/dealAssociations:remove
What HumDay can read from Google Ad Exchange Buyer II
These are the operations a schedule or a trigger can watch.
- GETList all products visible to the buyer (optionally filtered by the specified PQL query).
/v2beta1/accounts/{accountId}/products - GETList proposals. A filter expression (PQL query) may be specified to filter the results. To retrieve all finalized proposals, regardless if a proposal is being renegotiated, see th…
/v2beta1/accounts/{accountId}/proposals - GETList all reasons for which bids lost in the auction, with the number of bids that lost for each reason.
/v2beta1/{filterSetName}/losingBids - GETList all reasons for which bids were filtered, with the number of bids filtered for each reason.
/v2beta1/{filterSetName}/filteredBids - GETList all errors that occurred in bid responses, with the number of bid responses affected for each reason.
/v2beta1/{filterSetName}/bidResponseErrors - GETList all reasons that caused a bid request not to be sent for an impression, with the number of bid requests not sent for each reason.
/v2beta1/{filterSetName}/filteredBidRequests - GETList all reasons for which winning bids were not billable, with the number of bids not billed for each reason.
/v2beta1/{filterSetName}/nonBillableWinningBids - GETList all reasons for which bid responses were considered to have no applicable bids, with the number of bid responses affected for each reason.
/v2beta1/{filterSetName}/bidResponsesWithoutBids - GETRetrieves the requested filter set for the account with the given account ID.
/v2beta1/{name} - GETList all publisher profiles visible to the buyer
/v2beta1/accounts/{accountId}/publisherProfiles - GETList finalized proposals, regardless if a proposal is being renegotiated.
/v2beta1/accounts/{accountId}/finalizedProposals - GETLists all filter sets for the account with the given account ID.
/v2beta1/{ownerName}/filterSets - GETLists all metrics that are measured in terms of number of bids.
/v2beta1/{filterSetName}/bidMetrics - GETLists all metrics that are measured in terms of number of impressions.
/v2beta1/{filterSetName}/impressionMetrics - GETLists all the clients for the current sponsor buyer.
/v2beta1/accounts/{accountId}/clients - GETList all details associated with a specific reason for which bids were filtered, with the number of bids filtered for each detail.
/v2beta1/{filterSetName}/filteredBids/{creativeStatusId}/details - GETLists creatives.
/v2beta1/accounts/{accountId}/creatives - GETRetrieves an existing client user.
/v2beta1/accounts/{accountId}/clients/{clientAccountId}/users/{userId} - GETList all creatives associated with a specific reason for which bids were filtered, with the number of bids filtered for each creative.
/v2beta1/{filterSetName}/filteredBids/{creativeStatusId}/creatives - GETLists all the known client users for a specified sponsor buyer account ID.
/v2beta1/accounts/{accountId}/clients/{clientAccountId}/users - GETLists all the client users invitations for a client with a given account ID.
/v2beta1/accounts/{accountId}/clients/{clientAccountId}/invitations - GETList all creative-deal associations.
/v2beta1/accounts/{accountId}/creatives/{creativeId}/dealAssociations - GETGets the requested product by ID.
/v2beta1/accounts/{accountId}/products/{productId} - GETGets a creative.
/v2beta1/accounts/{accountId}/creatives/{creativeId} - GETGets a proposal given its ID.
/v2beta1/accounts/{accountId}/proposals/{proposalId} - GETGets a client buyer with a given client account ID.
/v2beta1/accounts/{accountId}/clients/{clientAccountId} - GETGets the requested publisher profile by id.
/v2beta1/accounts/{accountId}/publisherProfiles/{publisherProfileId} - GETRetrieves an existing client user invitation.
/v2beta1/accounts/{accountId}/clients/{clientAccountId}/invitations/{invitationId}
How automating Google Ad Exchange Buyer II works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Google Ad Exchange Buyer II account.
- Grant access, then go live. You approve the specific Google Ad Exchange Buyer II operations it may use — and only those.
Automate Google Ad Exchange Buyer II with these
- Gmail79 operations
- Google+9 operations
- Google Abusive Experience Report2 operations
- Google Accelerated Mobile Pages (AMP) URL1 operations
- Google Access Approval7 operations
- Google Access Context Manager9 operations
- Google ACME DNS2 operations
- Google Ad Exchange Buyer38 operations
- Google Ad Experience Report2 operations
- Google Admin SDK122 operations
- Google AdMob7 operations
- Google AdSense Host26 operations
Categories
Questions about Google Ad Exchange Buyer II automation
- Can HumDay connect to Google Ad Exchange Buyer II?
- Yes. HumDay reads Google Ad Exchange Buyer II's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 50 operations are documented.
- Do I need to write code to automate Google Ad Exchange Buyer II?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Ad Exchange Buyer II account.
- What can HumDay do in Google Ad Exchange Buyer II?
- 22 of the 50 documented operations change something in Google Ad Exchange Buyer II, and 28 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Ad Exchange Buyer II account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Ad Exchange Buyer II is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Ad Exchange Buyer II at adexchangebuyer.googleapis.com/$discovery/rest?version=v2beta1. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.