ads
POST /v1/ads/webhooks/{connection_id}/test
Send one signed example of a Zinn® Ads event to a webhook endpoint (za-192).
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.
Where your organisation id goes
This endpoint takes org_id as a field in the JSON body.
Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.
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/webhooks/{connection_id}/test \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ "event": <AdsWebhookEventName> }'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.webhook_test. Queues one example event (marked "test": true, ids all zero) to the endpoint; the delivery sweep sends it within a minute, signed exactly like a real event, and it appears in the endpoint's delivery log. A 422 refusal.adsconnect.webhookBadEvent for an unknown event and refusal.adsconnect.webhookNotVerified for an endpoint not verified yet (FIX-REFUSED).
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
org_id | string | No | — |
event | AdsWebhookEventName | Yes | A Zinn® Ads webhook event (za-192, docs/1006 §70). |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | object | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429