ads

GET /v1/ads/analytics/views

The saved analytics views of the organisations the caller can see (za-286).

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.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/analytics/views \
  -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. A saved view is a name over the /ads/analytics filters (params, exactly the analytics API's query parameters) and chart choices (chart: metric, board), shared by everyone in the organisation it was saved on. org_id narrows to that organisation. Ordered by organisation, then name.

Parameters

NameTypeRequiredWhat it is
org_id (query)stringNo—

Response

NameTypeRequiredWhat it is
dataAdsSavedView[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429