ads

POST /v1/ads/connections/{connection_id}/tracking/check

Run the tracking check and the recovery upload 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}/tracking/check \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

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.tracking_check. The same step the daily per-connection job runs before every audit; twice in one minute is one run. recovery_mode: validate checks the upload at the network and keeps nothing (a network with no validate-only mode is checked locally and sent nothing). 503 when the workflow could not be started.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Request body

NameTypeRequiredWhat it is
recovery_modestring<, validate>No—

Response

NameTypeRequiredWhat it is
connection_idstringYes—
startedbooleanYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503