ads
GET /v1/ads/connections/{connection_id}/grow
The account's operating plan — this week's "Suggestions to grow" and the calendar (za-85).
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}/grow \
-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 week's 3 to 5 ideas for the account, best evidence first — scale_test (a campaign earning at least the account's ROAS target over 14 days and losing at least 20% of its impressions to budget: +50% budget for 14 days, money in integer micros with its ISO currency), country (converts without its own campaign), competitor (a new brand on searches naming it) and experiment (a 50/50 landing-page test) — and the next 21 days' calendar (seasonal peaks, the monthly ad-copy refresh, the quarterly structure review and the account's scheduled reviews due in the next 7 days). Read from our own rows — never a network call; the suggestions are written once a week by the zinn-ads-grow Temporal schedule (docs/1006 §60). Nothing here changes the ad account.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
week | string | Yes | — |
generated_at | string | Yes | — |
data | AdsGrowSuggestion[] | Yes | — |
calendar | object[] | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 429