Field reference

Every field theStacc sends in a blog.published / blog.updated event:

Field	Type	Always sent?	Practical limits	What it is
`event`	string	Yes	enum: `blog.published` \| `blog.updated` \| `blog.unpublished` \| `blog.deleted` \| `test.ping`	Use this to route in your handler.
`blog_id`	string (UUID)	Yes	36 chars, or `preview-` + UUID for sample payloads	theStacc’s stable identifier. Use as your dedup / foreign key.
`author`	object \| `null`	Only when explicitly configured or cleared	`name`: 1–200 characters; `type`: `Person` or `Organization`	Optional blog byline. Omitted preserves the site default/current author; `null` resets to the site default. See below.
`title`	string	Yes	typically 50–120 chars	Blog title. Not HTML-escaped — your receiver renders it.
`slug`	string	Yes	typically up to ~50 chars, lowercase, hyphenated	URL-safe identifier. Stable across re-publishes unless the user edits it.
`content`	string (HTML)	Yes	typically 4,000–15,000 chars	Full blog HTML. Includes `<h2>`, `<p>`, `<ul>`, `<a>`, `<img>`, etc. The duplicate hero `<img>` is stripped (see note below).
`excerpt`	string \| `""`	Yes (may be empty)	typically 100–300 chars	Short summary, plain text.
`excerpt_short`	string \| `""`	Yes (may be empty)	word-boundary trimmed to roughly 256 chars	A truncated copy of `excerpt`. Use this when forwarding to a CMS with a strict Excerpt cap — notably Webflow’s default 256-char Excerpt field.
`meta_title`	string \| `null`	Yes	up to ~70 chars (SEO best practice)	Optimized SEO title. May equal `title`.
`meta_description`	string \| `null`	Yes	up to ~160 chars (SEO best practice)	Optimized SEO description.
`featured_image_url`	string (URL) \| `null`	Yes	`https://cdn.thestacc.com/...`	Public CDN URL for the hero image. Separate from `images[]`.
`categories`	string[]	Yes (may be `[]`)	typically 0–3 items	One blog can have multiple categories.
`tags`	string[]	Yes (may be `[]`)	typically 0–10 items	Loose keywords.
`keyword`	string \| `null`	Yes	typically 1–8 words	Focus keyword the blog targets. `null` when the blog has no focus keyword set.
`published_at`	string (ISO 8601 UTC)	Yes	always Z-suffixed UTC	When theStacc finalized this publish.
`images`	`{url, alt}[]`	Yes (may be `[]`)	typically 0–4 items	Every `<img>` URL embedded in the `content` body, in document order, deduped. Use it to self-host body images — see Self-hosting images. Does not include `featured_image_url`.
`ctas`	`{label, url, type}[]`	Yes (may be `[]`)	typically 0–12 items	The project’s Recommended Resources links (Content → Settings → CTAs) as structured data. `type` is `primary`, `secondary`, `youtube` or `social`. The same links are also rendered into `content` as a final `<section class="fairview-cta-resources">` block just before the locked footer, so a receiver that prints `content` as-is shows them; strip that section if you render `ctas` yourself. Empty when CTAs are switched off.
`idempotency_key`	string	Autopilot publishes only	`"{blog_id}:{lifecycle}"`	Stable across all retries of a single publish; different across separate publish intents. Dedup on this. See Idempotency & retries.
`publish_attempt`	integer	Autopilot publishes only	`1` on the first try, then `2`, `3`, …	The attempt counter for this publish lifecycle. `> 1` means theStacc is retrying after a transient failure. Useful for logging.

The hero image is stripped from content. Every generated blog carries its hero image both as featured_image_url and (originally) inlined as the first <img> in the body. theStacc removes that inline duplicate before sending, so content won’t render the hero twice and images[] won’t list the hero URL. Render the hero from featured_image_url and the body images from inside content (or mirror them via images[]).

Field length is not enforced at the API level. Postgres TEXT columns are unbounded, and theStacc-generated content stays well within the practical limits above. If you want hard caps in your database schema, the limits in the table are safe defaults.

Blog author

An explicitly configured byline is sent on first publication, republication, and Sync, including scheduled publishing:

{
  "event": "blog.published",
  "blog_id": "8f3e...",
  "author": {
    "name": "Rian Air Editorial Team",
    "type": "Organization"
  }
}

The example shows only the author-related fields. The normal blog payload also includes the article fields documented above. For a personal byline, send {"name": "Aditi Rao", "type": "Person"}. This identifies the author; it does not change the article’s blog format/category.

Incoming value	Receiver behavior
`author` omitted	Keep the current author on updates; use your site’s default on creation.
`author: {name, type}`	Validate and store the explicit name and type. Replace any previously configured author.
`author: null`	Clear the explicit author and fall back to the site’s default.

Do not use a truthiness check such as if (body.author) to decide whether to update: that would ignore an explicit reset. Check property presence:

const authorPatch = {};
if (Object.hasOwn(body, 'author')) {
  if (body.author === null) {
    authorPatch.authorName = null;
    authorPatch.authorType = null;
  } else {
    const author = body.author;
    if (typeof author !== 'object' || typeof author.name !== 'string'
        || !author.name.trim() || author.name.length > 200
        || !['Person', 'Organization'].includes(author.type)) {
      throw new Error('Invalid blog author');
    }
    authorPatch.authorName = author.name.trim();
    authorPatch.authorType = author.type;
  }
}
// Merge authorPatch into your existing validated article upsert, keyed by blog_id.
// Use the same mapping for blog.published AND blog.updated.

Website receiver checklist

Allow the optional field in your payload validator. Continue accepting older payloads without it and test.ping without article fields.
Store nullable author name and type alongside the article, or map them to an existing CMS byline field. No separate author-account creation is required for a text byline.
Handle both blog.published and blog.updated through the same article upsert by blog_id.
Render the effective author name on article pages as escaped text. Use your configured default when no explicit author exists. Update listing cards too if they display authors.
Set BlogPosting.author to {"@type": "Person", "name": "Aditi Rao"} or the corresponding Organization. The visible byline and structured data must agree. Escape < when embedding serialized JSON into an HTML script element.
Refresh page/build caches after updates so author changes appear on the live page.
Acknowledge only after the write succeeds, returning the existing CMS id and public URL. Never acknowledge an unsupported update as success.
Verify first publish, an author-only update, clearing the author, an old payload without the field, and a repeated delivery. Preserve the existing raw-body signature verification and deduplication behavior.

The scheduled publishing payload includes generated jsonld; its BlogPosting author follows this selection. Do not require jsonld on every delivery: manual and Sync payloads may omit it. Your site should maintain structured data from the stored author fields on every update.

Select existing site authors

Provide an optional public HTTPS author-list endpoint to show your site’s authors in a dropdown. Selected authors include an optional stable author.id alongside the existing name and type; manual names keep the previous shape. See Existing website authors for setup, response limits, and receiver handling.

Static sites

Webhooks

Blog author

Website receiver checklist

Select existing site authors

​Blog author

​Website receiver checklist

​Select existing site authors

Blog author

Website receiver checklist

Select existing site authors