SOAP API (Legacy)

🚧
The SOAP API is now classed as a legacy system. While we won’t be adding new features or functionality, we will maintain its availability and provide ongoing support. We recommend using our REST API for new calls and when updating existing SOAP calls. For more information, please visit our REST API documentation.

This SOAP API is now considered a legacy system. While we won’t be adding new features or functionality to it, we understand its importance in your current operations. Therefore, we are committed to maintaining its availability and providing ongoing support. This ensures that your operations relying on our SOAP API continue to function without disruption. However, we recommend using our REST API for new calls and when updating existing SOAP calls.

You can integrate N-able N-central with third-party applications. N-able N-central provides three integration points with third-party applications using our SOAP API:

Web Service APIs
Linking to N-able N-central Using URLs
Notification Acknowledgement Using XML

Additional information on using APIs with N-able N-central can also be found in the troubleshooting article, Accessing N-able N-central API functions.

Legacy API Availability Changes

As part of our ongoing commitment to strengthening the security posture of N-central, from N-central 2025.4 we are deprecating certain legacy API functionalities and removing access to APIs originally intended for internal use only.

The public SOAP EI API will no longer be accessible.
The public SOAP EI2 API will remain available.
The public REST API will remain available.

The below features will cease to function post-upgrade until they are migrated to newer APIs in future releases. Features impacted:

N-central Mobile APP
N-central Mobile Device Management (MDM)
External Data Feed (A new API is available under EI2 that is not affected)

To support transitional needs, we’ve introduced a new setting under:

Administration > Mail and Network Settings > Network Security > LEGACY APIS

This setting allows administrators to temporarily re-enable deprecated APIs.

❗️
Please note that re-enabling these APIs will expose the N-central server to potential malicious exploits.

EDF API Changes

As part of the removal of the EDF API users will need to start using the EI2 API in order to continue to access EDF functionality. Instructions can be located through our javadocs in the EI2 API documentation under the “edfsubmit” section.

/dms/javadoc_ei2/com/nable/nobj/ei2/ServerEI2_PortType.html