To correctly implement a custom control API in APISIX, your plugin should export a control_api() function that returns a table of API definitions (with methods, uris, and a handler function). The control API is only accessible via localhost (default: 127.0.0.1:9090) unless configured otherwise. See the official docs for plugin control API registration.

If your control_api() isn't being executed, the most common causes are: the plugin file isn't mounted or placed correctly, the plugin isn't listed in the plugins section of config.yaml (listing plugins overrides defaults, so include all you want enabled), the luaPath or extra_lua_path isn't set to include your plugin directory, or APISIX wasn't restarted after changes. If you're running in decoupled mode, make sure the plugin is in the data plane container, not the control plane. Also, ensure enable_control: true is set in your config and that you're accessing the endpoint via 127.0.0.1:9090 (or your configured control API address) source.

If all of the above are correct, enable debug logs and check for errors about plugin or control API registration in the APISIX logs. This will help pinpoint if the plugin is loaded and the control API is registered at runtime source.

Let me know if you want to dig into your config or logs for more targeted troubleshooting.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}