The open-source Django CMS adds a preview v3 REST API that lets scripts and AI agents create, edit, and publish content — with an OpenAPI schema endpoint so agents can discover it — while keeping AI out of the admin by default.
2026-08-28 · by Moe Ameen
Wagtail, the open-source Django content management system built by Torchbox, released version 8.0 on August 25, 2026. The headline addition is a preview of a new v3 REST API — and unlike the older read-only v2 API, this one can write. Authenticated clients can create, edit, publish and unpublish, move, copy, and revert content, and manage drafts and revisions, across pages, images, documents, snippets, redirects, sites, and locales. The team frames it as more than 50 admin operations exposed over HTTP.
The design leans toward machines reading and acting on content. The API is built on Django Ninja with Python type hints, it can return rich text as HTML or Markdown, and it ships a schema endpoint that auto-generates OpenAPI 3.1 documents — the point being that an AI agent or chatbot can fetch the schema, discover what operations exist, and drive the CMS deterministically. Access uses token authentication and Wagtail's existing permissions model, with public read access available for headless sites.
The philosophy Wagtail attached to the release is the notable part: "a CMS with AI, not an AI CMS." No AI features are switched on inside the admin by default — teams opt into the separate Wagtail AI package if they want them. The bet is that the durable value is a clean, typed, writable API that both humans and agents can use, rather than bolted-on generation buttons. Cited example workflows include bulk SEO fixes (an agent rewriting weak page search descriptions across a site), content importers, and migrations between systems. Wagtail 8.0 also adds custom base page models, a permission-policy registry, and support for Django 6.1.
The v3 API is explicitly a preview — Wagtail says it may change in backwards-incompatible ways in any release until it stabilizes, so treat endpoint shapes and behavior as a moving target and confirm specifics in the official release notes.
The interesting thing about Wagtail 8.0 for creators is not the API itself — most creators won't touch Django — it's what it confirms: content operations are becoming pipelines that machines run end to end. Wagtail is doing that for the website, making the CMS a programmable, agent-discoverable endpoint. Kompozy already does the same thing for everything that lives off your website — the social, video, and email surfaces a CMS was never built to reach. The two sit on opposite ends of one content operation.
Here's how a creator acts on this today. Kompozy takes one source and generates the whole content set — Persona Shorts and HeyGen avatar video, Clipped Shorts from long footage, brand-exact Carousel Posts, Quote Graphics, Text Posts, plus a full Blog Article and Email Newsletter — every output held to one Persona Brief. It then schedules and publishes across the eight primary social platforms plus email, and pushes blog content to destinations including WordPress, GHL Blog, or a Custom Webhook — the same kind of programmatic endpoint Wagtail's new API exposes. So the blog article Kompozy writes can flow into your site while the same idea ships as video, carousels, and posts everywhere your audience scrolls. Wagtail makes your website agent-ready; Kompozy is the engine that produces and distributes the content, on autopilot, across the platforms the CMS can't touch.
Released August 25, 2026, Wagtail 8.0 adds a preview v3 REST API that can write — create, edit, publish, move, copy, and revert content across pages, images, documents, and snippets — with an OpenAPI 3.1 schema endpoint aimed at AI agents. It also adds custom base page models, a permission-policy registry, and Django 6.1 support.
No — Wagtail frames it as "a CMS with AI, not an AI CMS." No AI features are enabled in the admin by default; the separate Wagtail AI package is opt-in. The 8.0 work is a typed, writable API that both humans and AI agents can use, not built-in generation.
Not yet. Wagtail designates the v3 API a preview and warns it may change in backwards-incompatible ways in any release until it stabilizes. Confirm endpoint details against the official Wagtail 8.0 release notes before building on it.
No. Wagtail is a website CMS — it stores and serves your site content. It generates no social video, captions, or carousels and publishes to no social platform. For that half of the job, pair it with a content engine like Kompozy, which generates the full set and publishes across the eight primary social platforms plus email.