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

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}/outcomes \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "outcomes": <AdsOutcomeIn[]> }'

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.outcomes_received. Up to 500 per request (send pages for a back-fill; no limit on pages). Idempotent per (kind, external_ref): the same order twice is stored once, and a later copy that carries a click id the first lacked fills it in. external_ref is the order / trial id in YOUR system and is the transaction id every upload carries, so the network never counts one outcome twice. A plain email is SHA-256-hashed at the door and dropped. 201 when any was new.

Parameters

Request body

Response

Errors this endpoint can return

401 · 403 · 404 · 422 · 429