ads
GET /v1/ads/connections/{connection_id}/video
The account's Video and Demand Gen reading and its YouTube channel (za-201).
Authentication
Send an API key as a bearer token. The key must carry the ads.view 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 GET https://api.zinndigital.com/v1/ads/connections/{connection_id}/video \
-H "Authorization: Bearer zdk_live_…"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.view. The reading the connection's daily audit stored (docs/1006 §80) — never a network call in the request: each enabled Video and Demand Gen campaign with the people it reached and how often each saw an ad, its frequency caps, the placements its money went to, click-through beside view-through conversions; what all video campaigns claim against the sales the customer's own source recorded (real_sales, null with no source); and the YouTube link state of the videos the ads use. reading is null until the first audit (a Google account only). Changes are approve-first findings (GET /v1/ads/connections/{id}/findings).
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | object | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 429