ads

GET /v1/public/ads-wordpress/zaraz

The plugin's Zaraz step list - the zone connected for this site and what an install would write.

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 GET https://api.zinndigital.com/v1/public/ads-wordpress/zaraz \
  -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 (docs/1006.d/features/za-132-133-zarazsync.md §za-312). Site token only. The zone is found from the site's own host (its name, then each parent): zone_names lists the candidates, connection is the org's za-131 connection for that zone (or null), hub_networks the tracking-hub networks an install would write and skipped those Zaraz cannot run from a public id. The same connection row the dashboard's sync, drift and 30-day undo cover.

Response

NameTypeRequiredWhat it is
dataAdsWordPressZarazYes—

Errors this endpoint can return

401 · 429