ads
POST /v1/ads/connections/{connection_id}/audiences/{audience_id}/sync
Send a Customer Match list's difference to the network now.
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}/audiences/{audience_id}/sync \
-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.manage; audit action ads.audience_sync_requested. Starts the sync workflow for the account (one run per account per minute). The daily run does the same.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
audience_id (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
sync_started | boolean | Yes | — |
audience | AdsAudience | Yes | A customer's own Customer Match list (docs/1006 §72). Counts only, never an identifier. |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429