ApiCMS vs traditional REST plugins: why a native CMS API wins

Two different ways to have an API on a CMS

Almost every CMS can expose a REST API: WordPress has a core REST API plus plugins like WPGraphQL or WP REST API Controller, other CMSs rely on third-party plugins. ApiCms takes a different approach: the API isn't an external add-on, it's a native part of the CMS from the initial design.

The real limits of REST plugins added afterward

A REST plugin installed on a CMS designed for the classic web admin brings typical problems: overhead from an extra translation layer between the plugin and the core, risk of breaking changes when the CMS updates and the plugin falls behind, permissions and authentication often handled differently from the rest of the system, with a larger attack surface to keep under control.

What changes with a native API

With ApiCms, every action available via API (creating an article or product, updating the menu, uploading an image) is the exact same function used by the web admin — not a parallel layer. This means no misalignment, authentication with the same token system as the CMS, and every new CMS feature is automatically available via API too, without waiting for a separate plugin update.

The practical advantage: driving the site through chat

With a reliable native API, it becomes realistic to drive the entire site by writing natural-language requests to an AI assistant, which translates the request into direct API calls — no FTP, no admin panel to navigate by hand. This is the real use case that drove ApiCms's architectural choice from the start: the CMS as drivable infrastructure, not just a panel to click through.