Ship to your CMS — or pull it headless
Push finished articles to WordPress, Ghost, or Webflow in one click. Or skip the CMS entirely and fetch them through our read-only Content API — the same headless publishing most competitors don't offer.
Draftwave → your CMS
Approve an article and the connector publishes it for you.
- WordPress Available now
- Ghost Next
- Webflow Next
Your app → Content API
const res = await fetch(
"https://cdn.draftwave.io/v1/articles" +
"?site=SITE_ID&limit=10",
{ headers: {
Authorization: "Bearer pk_live_xxx"
} }
);
const { data } = await res.json();Publishable keys are read-only and origin-lockable — safe to ship in a browser.
One click, or fully hands-free
Publishing is a deliberate action by default: you approve, then push. When you trust the pipeline on a given site, opt into scheduled autopilot — rate-limited, per site — and Draftwave keeps the queue moving without you. The benefit is control when you want it and leverage when you don't.
A content backend developers actually want
The Content API returns clean, ready-to-render articles — HTML, excerpt, FAQ, and inject-ready JSON-LD — plus sitemap and RSS endpoints and an incremental manifest for static builds. It's edge-cached on Cloudflare, so it's fast and nearly free to serve. Pair it with webhooks and your JAMstack site rebuilds itself the moment you approve a post.
Frequently asked questions
Which CMSs can Draftwave publish to?
WordPress first, with Ghost and Webflow next. Approving an article runs the connector that pushes it to your CMS. You can also publish headlessly and pull the content via the Content API instead.
What is the headless Content API?
A read-only, edge-cached API that lets any frontend — a Vue or Next site, a static build, a mobile app — fetch your published articles with a publishable key. Draftwave becomes a headless CMS. It's the same API this marketing blog runs on.
Is autopublishing safe?
Human-approve is the default: generation produces drafts in a review queue, and publishing is a separate action. Autopublish is strictly opt-in per site and rate-limited, so you never wake up to content you didn't see.
How do static sites know when to rebuild?
Webhooks. Draftwave POSTs site.article.published / updated / unpublished events with an HMAC signature to a URL you register — typically your deploy hook — so a JAMstack site rebuilds automatically when you approve new content.