Webhook Events

Notification sent event

Built for agents. One event for every notification we would email the account owner: a scheduled post failed to publish (type: post_failed), a connected account was disconnected (type: account_disconnected), or a removed team member's recently used API key was handed to the owner (type: api_key_handed_over).

It carries the email's subject and text, references to the post or account, and the actions that resolve it, so an agent subscribes to one event and handles every notification the same way.

Agents or state sync

Subscribe to notification.sent when an agent or automation reads the alert and acts on it. Subscribe to post.platform.failed, post.failed, post.partial and account.disconnected when your system keeps post and account state in sync: they carry the structured post or account and fire on every state change.

When it fires

Once for each such notification, in near real time, regardless of the user's email toggles, and even when the owner has no email address or the email is held back by the sender's limits. It fires alongside post.failed and account.disconnected, which stay as they are.

The user's notification channel (Slack or Telegram) follows the email toggles, so it only receives the alerts whose toggle is on. The exception is api_key_handed_over (category securityAlerts), which has no toggle and is always delivered.

  • post_failed: once the failure is final (a permanent error, or a temporary one on its last retry), once per publish attempt that failed, for scheduled posts only (not "post now"). refs.platforms lists every platform that failed in that attempt.
  • account_disconnected: every time an account is disconnected, never for creator-profile accounts. reason says why.
  • api_key_handed_over: once per API key, when a departing team member's key used in the last 7 days moves to the workspace owner. It stops working within 24 hours: create a new key and switch to it. refs.apiKey carries the key id, preview and expiry.

Payload notes

text is the email body without the greeting. When your content retention is set to keep no content, the post text is replaced by Content not retained and each platform error by a generic description of its category.

How to act

Each entry of actions is a public API call with the ids already in the path: retry_post (retryPost, POST /v1/posts/{postId}/retry), reconnect_account (getConnectUrl, GET /v1/connect/{platform}) and check_account (getAccountHealth, GET /v1/accounts/{accountId}/health).

Who receives it

Endpoints subscribed to notification.sent. Scoped endpoints receive it for their profiles and accounts. Restricted keys need the publishing resource group.

postWebhooknotification.sent

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'notification.sent' required
timestampstring date-time required

UTC time at which Zernio generated this event. Retries and redeliveries keep the original value.

Example payload

{
  "profiles": [
    {
      "externalId": "tenant_42"
    }
  ]
}

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.