API Overview
Use the classic API, Eloquent models, routes, validators, and response helpers according to the actual job.
This section covers the integration surface of Evolution CMS, from classic API usage to modern platform capabilities.
Evolution CMS can be integrated at several levels. Older projects often use the classic API and direct DB access. Newer projects may add package services, versioned endpoints, passkeys, queue-like task tooling, webhooks, AI integrations, or MCP servers.
This section keeps those approaches in one place so you can choose the right level of abstraction for the job instead of forcing everything into one pattern.
Use the classic API, Eloquent models, routes, validators, and response helpers according to the actual job.
Separate manager auth, web-user auth, protected content, and passkey flows instead of treating them as one thing.
Use mail, webhook, and notification flows to move Evolution events into CRM, ops, and business systems.
Current AI and MCP tooling in Evolution centers on eAi, eMCP, and adjacent workflow packages.