Inquiry regarding API changes following the recent update.

SungYeon Kim

February 10, 2026 23:47

Existing developers have been facing persistent challenges following the recent series of Gen6 updates. 

Applying the latest trends for optimization is desirable; however, we need to find ways to resolve the issues existing developers are encountering to ensure a smooth transition.

We are currently working on the development and testing of AI plugins compatible with versions earlier than 6.0.3.

The recent 6.1 update appears to have altered the response code behavior for the GET /api/getEvents API.

See the attached image for details.

   Nxwitness 6.0.6 (GET /api/getEvents)                Nxwitness 6.1 (GET /api/getEvents)     

Regarding the issues mentioned above, I would like to inquire about the following:

1. Does the team plan to discontinue support for this API information in versions 6.1 and later?
2. Is it possible to provide a patch that would allow us to continue using this specific functionality?
3. Must we limit our usage to products version 6.0 and below in order to maintain this functionality?

We look forward to your response, as this is critical for our ongoing AI plugin development. Your prompt response would be greatly appreciated.

0

• 

  Sergey Yuldashev

  • Network Optix team

  February 20, 2026 22:34

  Hello SungYeon Kim ,

   

  First of all, please refer to the API changelog for the clarification:

  https://meta.nxvms.com/doc/developers/api-tool/apichangelog

  More specifically - please take a closer look at the deprecation notice for certain methods:

  

   

  Please also note that outside the deprecation scope, the data structures and contents that could be returned in response to certain API calls are prone to change.

  In order to accommodate those changes and allow smoother transition we are usually publishing the developer preview versions(something like early alpha) 6-9 months before the official release. Thus we ensure our tech partners have access to the breaking changes documentation and could rebase their code accordingly if needed.

  Same happened for 6.1 - so this could hardly be called as something unexpected.

  Now to your questions:

  Does the team plan to discontinue support for this API information in versions 6.1 and later?

  If by API information you mean the method - it is claimed deprecated - i.e. it will be enabled for a while in the current state. But it is strongly recommended to rebase any code dependent on it.
  This method will not be getting any changes/updates moving forward except for being disabled in the future versions.

   

  Is it possible to provide a patch that would allow us to continue using this specific functionality?

  No, it will be impossible due to deprecation. I would recommend you inspect other existing methods especially those that were marked as the “modern replacement”.

  Must we limit our usage to products version 6.0 and below in order to maintain this functionality?

  If this data structure section is a main selling point/killer feature that makes your users favor the product, then probably yes. That said, I am pretty sure you will be able to find the method suitable for you among others for your application.

  And please take into account that:

  1. There will be no fresh patches for 6.0 in the future(including ones that could contain security updates)
  2. New capabilities are respectively being delivered only with newer versions

  0

Please sign in to leave a comment.