ads

GET /v1/ads/connections/{connection_id}/rules/{rule_id}/runs

A rule's run log — every run, what it read and what it did (za-196).

All ads endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The key must carry the ads.view 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 GET https://api.zinndigital.com/v1/ads/connections/{connection_id}/rules/{rule_id}/runs \
  -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.view. Newest first, the last 90 days. Each run says how many campaigns it checked and, for every campaign that met the condition, the reading and the outcome: applied / queued (waiting for approval) / refused (a guard said no — reason is its code) / cooldown / ownerLocked / learning / notified / failed, with the change id to approve or undo.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—
rule_id (path)stringYes—

Response

NameTypeRequiredWhat it is
dataAdsRuleRun[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 429