ads

POST /v1/ads/connections/{connection_id}/microsoft/import-google

Queue the ready Google Ads Search campaigns as pending Microsoft changes (za-39).

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.manage 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 POST https://api.zinndigital.com/v1/ads/connections/{connection_id}/microsoft/import-google \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "google_connection_id": <string> }'

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.manage; audit action ads.microsoft_import_google. Each ready campaign (or only campaign_ids) becomes ONE pending campaigns:mutate build change on the Microsoft connection — nothing is sent until a person approves it, and the kill switch, good standing and spend ceiling are checked again when it is applied. A month of the imported daily budgets is checked against the Zinn® Ads plan first (noAdsPlan, spendBracket). Nothing left to queue is 422 refusal.adsconnect.importNothing.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Request body

NameTypeRequiredWhat it is
google_connection_idstringYes—
campaign_idsstring[]No—
max_cpc_microsintegerNo—

Response

NameTypeRequiredWhat it is
connection_idstringYes—
google_connection_idstringYes—
currencystringYes—
dataobject[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429