ads

GET /v1/ads/zaraz/connections/{connection_id}/sync

The zone's sync state - drift against the agreed version and the hub, and the versions.

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.

Where your organisation id goes

This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.

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 GET https://api.zinndigital.com/v1/ads/zaraz/connections/{connection_id}/sync \
  -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-133 (docs/1006 §110). Gated on ads.view. drift.state is not_installed, in_sync, edited_in_cloudflare, hub_ahead or both, as of drift_checked_at (the daily sweep, or a refresh). Versions from the last undo_days days can be restored.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—
org_id (query)stringNo—

Response

NameTypeRequiredWhat it is
dataAdsZarazSyncYes—

Errors this endpoint can return

401 · 403 · 404 · 429