ads

POST /v1/public/ads-wordpress/zaraz/check

Re-check the connected zone's token and permissions, from wp-admin (writes nothing).

All ads endpoints

All developer docs →

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

Authentication

This endpoint does not take an API key. It takes its own credential, issued to the plugin or service that calls it, as a bearer token; see the description above.

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/public/ads-wordpress/zaraz/check \
  -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

za-312. Site token only; audit action ads.zaraz_check. When the token passes, the zone's configuration is also read (nothing written) so getAdsWordPressZaraz knows the zone's consent switch before the first install; a failed read leaves the check's answer. 404 (refusal.adsconnect.zaraz.noSuchConnection) until the site's zone is connected. Refusals as checkAdsZarazConnection.

Response

NameTypeRequiredWhat it is
dataAdsZarazConnectionYesA Cloudflare zone connected for Zaraz (za-131). The token is in Vault, never here; token_hint is its last four characters.

Errors this endpoint can return

401 · 404 · 422 · 429