Legacy API Protocols

Maho keeps the original Magento 1 API entry points alongside the modern v2 API:

These paths are handled by the original Mage_Api_*Controller classes, not by the API Platform kernel that serves the v2 API. Two things gate whether they actually respond.

Every protocol is disabled by default

Every protocol (the modern rest_v2, graphql, admin_graphql and the legacy legacy_rest, soap, v2_soap, xmlrpc, jsonrpc) defaults to off. Enable only the protocols you use in System → Configuration → Services → API → API Protocols. A disabled path returns 404 at the entry point.

SOAP / XML-RPC / JSON-RPC need optional packages

Those adapters build on Laminas components that are not installed by default - they are declared under suggest in composer.json. To use them, install the matching package(s):

composer require laminas/laminas-soap          # SOAP (soap, v2_soap)
composer require laminas/laminas-xmlrpc         # XML-RPC (xmlrpc)
composer require laminas/laminas-json-server    # JSON-RPC (jsonrpc)

Without them, an enabled legacy protocol errors when it tries to instantiate the adapter. The legacy REST API at /api/rest and the modern REST v2 / GraphQL API have no such dependency.

Web server routing

The legacy paths must reach Maho's normal front controller (index.php), not the v2 API entry point (rest.php). The bundled public/.htaccess already excludes them from the rest.php rewrite; if you use nginx, Caddy, or a custom Apache configuration, replicate that exclusion as shown in Web Server Configuration.