Integrate Anything with Nx Witness

Using HTTP Generic Events & Actions.

Nx Witness supports HTTP API requests through the Nx Server API - a comprehensive, standard RESTful API for integrating 3rd party devices and software systems.


Why did we choose a RESTful API?

  • REST enables any interface between systems using HTTP to obtain data and generate operations on those data in all possible formats, such as XML and JSON.
  • REST is a stateless client/server protocol. That means any HTTP request contains all the necessary information to execute, which and neither the client nor the server need to remember any previous state to satisfy it. 
  • REST has become a software development standard. Pretty much everyone out there - including Facebook, Google, Twitter - has begun using REST and as a result there is a vast knowledge and experience base out there among software developers.

Using Generic Events

 Send Generic Events from 3rd party Devices or Systems into Nx Witness


When a user sends a Generic Event (aka a CreateEvent API) call to any Nx Witness Server it is received as a Generic Event. 

Nx Witness - when first installed - has a default rule to show all Generic Events received in the notifications panel on the Nx Witness Desktop app.

Generic events that are received can then be used to create system rules - such as triggering an I/O, triggering a PTZ Preset-as-an-Action, launching an Alarm Layout, creating a Bookmark, or even sending an HTTP Request to a different 3rd party device or system.

(better if viewed full screen)

    Try it for yourself:

    • Download and install the Nx Witness Desktop app (Mac, Ubuntu, or Windows) 
    • Log in to the Nx Demo System (host:, username : demo, password : nxwitness)
    • Copy and paste the following string into your browser and you should see a notification appear in your client that says Just-a-Test : 
    Check your notifications bar for this message!

    Check your notifications bar for this message!

    Using HTTP Actions

    Send HTTP Requests as an Action from Nx Witness to a 3rd party Device or System.


    HTTP Request-as-an-Action is a feature of Nx Witness that allows users to create a rule that sends an HTTP POST or GET request over the network to a targeted service or device.

    This allows Nx Witness to send alerts to 3rd party systems or devices, which can then be used in those devices or systems to trigger additional actions.

    Combining HTTP Generic Events and HTTP Request-as-an-Action allows users to use Nx Witness as a central event nexus - with building automation, fire, alarm, access control, lighting, and HVAC systems all combined with and working together with an IP Video platform. 

    With the coming of deep learning-driven video applications and with Nx Witness Server Hive Architecture Nx Witness has huge potential as a reliable, responsive, distributed IOT-type solution.

    Try it for yourself:

    For purposes of this demo you'll need your own Nx Witness System (use the Free Trial!), cameras, and 3rd party system to integrate with.

    • Open your Nx Witness Desktop App
    • Navigate to the Alarm/Event Rules Dialog
    • Click the Add button to create a new rule.
    • Configure your triggering Event
    • In the Action column select Do HTTP request.
    • Click the Advanced Button on the right top of the Alarm/Event Rules Dialog.
    • Choose your Interval of Action.
    • In HTTP URL enter the listen endpoint for the request.
    • in Login and Password enter any credentials you may need for authenticating with the device or service you are sending the HTTP Request to. Supports Basic and Digest authentication.