ads
GET /v1/ads/connections/{connection_id}/autopilot
What the autopilot does on this account.
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}/autopilot \
-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 (za-14, docs/1006 §53). Each step the house autopilot runs on a customer's account (add a wasteful search term as a negative, pause a keyword that spent its maturity clicks with no conversion, add a converting search term as a phrase keyword) with the account's mode for it: auto (sent, with a 30-day Undo), approve (kept as a change for a person to approve) or off (never tried). Every write still passes the account's guards (good standing, spend ceilings, hold until a sale, ROAS target). last_run is what the latest finished audit did, null before the first one. Read from stored rows — never a network call in the request.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | AdsAutopilot | Yes | za-14 — what the autopilot does on one connected ad account. |
Errors this endpoint can return
401 · 403 · 404 · 429