ZEzernio
Webhook Events

Campaign submission rejected event

Fired when an operator rejects a submission.

postWebhookcampaign_submission.rejected

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. It identifies the event only, never an account or other resource.

testboolean

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

event'campaign_submission.received' | 'campaign_submission.flagged' | 'campaign_submission.pending_review' | 'campaign_submission.approved' | 'campaign_submission.rejected' required
timestampstring date-time required

UTC time at which Zernio generated this event (set once when the event payload is built, before delivery is queued). Retries and redeliveries keep the original value, so it reflects the event, not the delivery attempt.

Example payload

{
  "profiles": [
    {
      "externalId": "tenant_42"
    }
  ],
  "submission": {
    "platform": "tiktok",
    "status": "tracking",
    "flags": [
      {
        "code": "duplicate_post"
      }
    ]
  }
}

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.