ads

POST /v1/ads/connections/{connection_id}/audits

Run the connection's audit now (a Temporal workflow).

All ads endpoints

All developer docs →

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}/audits \
  -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.audit_run. Starts the same per-connection workflow the daily fan-out runs; twice in one minute is one run. Every change it finds is sent through the approve-first queue (nothing is applied unless that class is auto). 503 when the workflow could not be started.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Response

NameTypeRequiredWhat it is
connection_idstringYes—
startedbooleanYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503