Webhooks

The dashboard Integrations → Webhook tab shows the intended inbound payload for a CMS publish event. Treat it as a contract preview, not a live public endpoint.

HMAC-signed ingest with replay protection is the target. It is not a documented, generally available URL today. Prefer the REST API to create campaigns, or RSS for feed-driven stories.

Intended payload

json

{
  "event": "content.published",
  "id": "article-123",
  "url": "https://publisher.example/story",
  "title": "Story title",
  "summary": "Optional summary",
  "image_url": "https://publisher.example/image.jpg",
  "language": "en",
  "published_at": "2026-08-17T12:00:00.000Z",
  "tags": ["news"]
}

When ingest ships, expect HTTPS, a shared secret, an HMAC header, and a timestamp so replays can be rejected. Do not send subscriber PII in this payload.

Outbound webhooks

Outbound delivery receipts are not published yet.

REST API
WordPress

Webhooks

Intended payload

Outbound webhooks

Related