ads

PUT /v1/ads/connections/{connection_id}/video

Save (or clear) the customer's own YouTube channel on a Google connection (za-201).

All ads endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The key must carry the ads.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X PUT https://api.zinndigital.com/v1/ads/connections/{connection_id}/video \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "youtube_channel_id": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Gated on ads.manage; audit action ads.youtube_channel_set / ads.youtube_channel_cleared. youtube_channel_id is the channel ID from YouTube Studio (UC + 22 characters); "" clears it. Nothing changes at Google: the next daily audit suggests linking each video of this channel the ads use (Google Ads DataLinkService), each one a person's approval with an Undo, and the channel owner then approves the link in YouTube Studio. A saved channel also unlocks the reach objective on Video and Demand Gen campaigns. 422 youtubeChannelInvalid for any other value; 422 platformNotSupported on a connection that is not Google.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Request body

NameTypeRequiredWhat it is
youtube_channel_idstringYes—

Response

NameTypeRequiredWhat it is
dataobjectYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429