ZEzernio
Webhook Events

Ad updated event

An ad was edited through Zernio (source: "zernio"), or outside Zernio and detected by the sync (source: "platform").

When it fires

Fires once, to the owner of the edited ad. Outside edits arrive up to one sync interval late. Every edit is announced, so use the event id to drop repeats.

Payload notes

changes lists the edited fields: name, status (the ad's own on/off switch), budget, targeting or creative. Ignore unknown values; new ones can be added.

Reading the change

The event never carries old or new values, so read the ad. platformId can change when a LinkedIn creative is replaced, while adId stays stable.

When it does not fire

From the sync, changes covers only name and status. Budget, bid, schedule and targeting edits made outside Zernio, tracking tag edits and history loaded at connect are not announced. Ad rule changes arrive as ad_rule.triggered.

postWebhookad.updated

Payload

idstring required

Stable webhook event ID: the dedupe key, also sent as the X-Zernio-Event-Id header and identical on every retry and redelivery.

testboolean

Always true when present: only a sample sent by POST /v1/webhooks/test with an event carries it. Real deliveries never do.

event'ad.updated' required
changesstring[] required

Fields edited by this request. status is the ad's own on/off switch. Ignore values you do not know.

source'zernio' | 'platform' required

Where the edit was made. zernio for edits through Zernio, platform for edits the sync detected outside Zernio.

timestampstring date-time required

UTC time at which Zernio generated this event.

Example payload

{
  "profiles": [
    {
      "externalId": "tenant_42"
    }
  ],
  "account": {
    "platform": "tiktokads"
  }
}

Response

Webhook received successfully

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.