Starter · Part of Knowledge Management
Article authoring API
Backend authoring endpoints — create draft, list with state filters, fetch detail, publish — with audience-aware visibility from the first save. The API is what the editor UI, seed pipelines, and integrations all write through.
For the operator
Knowledge ops uses the editor UI day-to-day; the same endpoints power seed scripts when bulk-loading legacy content and integrations when a connected system needs to push articles in. One API, one data shape, full audit on every write.
Business impact
A single authoring path that the editor and integrations share eliminates the failure mode where the UI knows about a field the API doesn't — or vice versa. The KB stays internally consistent at the database level, not as a hopeful contract between layers.