Official Local API for System Configuration and Service Management

Hello QNAP Team,

I would like to request an officially supported local management API for common system configuration settings and service management.

While many settings are available through the QTS web interface, there is currently no documented or supported way to automate them. This makes it difficult to integrate a QNAP NAS into automation platforms such as Home Assistant or enterprise management tools without relying on undocumented internal endpoints that may change between firmware releases.

Some examples of settings that would be valuable to expose include:

  • Enable/disable SSH

  • Enable/disable Telnet

  • Enable/disable FTP

  • Enable/disable the Web Server

  • Configure SMB settings

    • Minimum SMB version

    • Maximum SMB version

    • SMB signing

  • Configure NFS and AFP services

  • Other commonly managed network and security settings

Example Use Cases

  • Enable SSH only when maintenance is required, then automatically disable it after a defined period.

  • Temporarily change SMB compatibility settings for legacy devices, then restore secure defaults.

  • Integrate QNAP with Home Assistant or other automation platforms for physical buttons, dashboards, or scheduled maintenance workflows.

  • Manage multiple NAS devices using scripts or centralized administration tools.

  • Support enterprise configuration management solutions such as Ansible or PowerShell.

Why an Official API?

Today, advanced users often resort to reverse engineering the QTS web interface or calling undocumented CGI endpoints. These approaches can break after firmware updates because they are not part of a supported interface.

An officially documented local API would provide:

  • Stable automation across QTS updates

  • Better integration with third-party automation platforms

  • Reduced reliance on unsupported methods

  • A more powerful and extensible platform for both home users and businesses

Security

This should remain a local, authenticated API protected by the existing QTS authentication and permissions model. There is no need for cloud access—only a supported method for trusted local automation and management.

Thank you for considering this feature. I believe it would significantly improve QNAP’s integration with modern automation and systems management platforms while reducing the need for unsupported workarounds.

Regarding API usage, you can achieve the functionality you mentioned by applying for QNAP Developer access. Thanks!

Developer Center | QNAP