Three integration patterns, each with a live example: the JavaScript Editor API for in-editor control, the REST API for server-to-server or browser-based calls, and the Document stateless API for backend pipelines – no active editor instance required. Select a tab to get started.
The Frontend Editor API lets you execute AI prompts directly from your application. A single prompt can rewrite and restructure an entire document without opening AI Chat. See the full API reference.
The Actions endpoint runs stateless transforms on any content you pass to it, with responses streamed over Server-Sent Events. This demo calls it from the browser to generate a title and a meta description for a blog post. The same call works from your backend. See the full API reference.
The Document Processing endpoint takes a prompt and an HTML document and returns a transformed version. It is designed for server-side workflows like CMS publish hooks, content pipelines, and batch translation. This demo runs the flow in the browser for visibility, but the same call is at home in your backend. This endpoint is experimental. See the full API reference.
This demo contains just a small subset of available CKEditor features. You are free to add more features to CKEditor regardless what editor type/toolbar you choose.
Read more about the AI programmatic capabilities in the documentation.
