Update account callouts
Edits existing Google Ads callouts in place; the change applies everywhere that callout is used.
Send updates with assetResourceName and the fields to change. An asset is shared: changes affect every attachment using it. Omitted fields stay unchanged. The operation consumes the Google operations budget and invalidates affected cached lists.
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.adaccounts.updateAccountCallouts({ body: { accountId: 'account_abc123', updates: [ { assetResourceName: 'Example', }, ], },});console.log(data);{ "updated": 0, "customerId": "string"}Add account callouts
Creates callouts and attaches them at account level in Google Ads so they can show on ads across all campaigns. Creates assets and customer_asset links for this Google customer. Links apply at account level.
Remove account callout
Detaches a callout from the Google Ads account level, leaving it on any campaigns or ad groups that still use it. Removes the customer_asset attachment only. The underlying shared asset and its campaign or ad-group attachments remain. Fields go in the query string. A JSON body with the same fields is also accepted and, when sent, the query string is ignored.