ads
GET /v1/ads/report/rows
Daily campaign rows for Looker Studio (za-200).
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.
Where your organisation id goes
This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.
Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.
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/report/rows?start=<start>&end=<end> \
-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. One row per day, ad account and campaign over start..end (inclusive, at most 400 days) for the organisations the caller may view; org_id narrows to that organisation and its clients. Built for the Zinn® Ads Looker Studio community connector, which authenticates with an API key minted on ONE client organisation with only the ads.view scope, so the key reads that client and nothing else. Spend and value are integer micros of the account currency (currency on every row); conversions are thousandths. Paged: follow next_offset until it is null. Stored rows only - never a network call in the request.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
org_id (query) | string | No | — |
start (query) | string | Yes | — |
end (query) | string | Yes | — |
offset (query) | integer | No | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | AdsReportRows | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429