Get NX events to third party application ?

Answered

Carette

January 30, 2026 11:12

Hi Network Optics

We'd like to get all NX Server events (camera, detection, AI, system,…) from NX server to our third party apps (which is used for global security managment).

We found the avalability to push event to the NX server but not to get (pull) from NX server to our application.

Is there a possibility :

1. To get events from NX server to our app with polling method

2. To push all events from the NX server to our third party app with webhook ?

We found too in the rules options to push event to a HTTP Post but this for one event only and we'd like to have for all events .

Thanks for your help

0

• 

  Ichiro

  • Network Optix team

  January 30, 2026 20:41 Edited

  Hi 

  You are on the right track. 
  The API endpoint you identified is indeed the standard way to retrieve detailed metadata for specific objects.

  That said, depending on your goal—such as building a real-time dashboard versus generating historical reports—there are several ways to extract data from Nx Meta / Nx Witness.

   

  1. Query-Based Approach (Nx REST Media Server API)

  As you mentioned, the REST API is the most straightforward option for historical analysis or on-demand data retrieval.

  • Endpoint: GET /rest/v4/events/log
  • Use case: Polling or retrieving events from the Mediaserver within a specific time range
  • Workflow:
    1. Query /rest/v4/events/log with filters such as time range, camera, or attributes.
    2. Use the returned results to build your own application logic or dashboard.

  This approach is well suited for reports, analytics, or dashboards that may not require real-time updates.

   

  2. Event-Push Approach (Semi-Real-Time via Rules Engine)

  If your goal is to send data to an external system immediately when an event occurs—without continuous API polling—you can use the built-in Rules Engine.

  • Workflow:

    Create a rule: When: an event occurs → Do: send an HTTP(S) request.

  • Available placeholders (examples):

    • {event.type} – Event type
    • {event.cameraId} – Unique camera ID
    • {event.timestamp} – Event timestamp
    • {event.caption} – Event caption
    • {event.description} – Can be used to embed custom or additional metadata

    This approach is simple to set up and allows near real-time data delivery. Your external system only needs a web endpoint (webhook) to receive the POST requests, with any additional business logic handled outside Nx.

   

  Hope this helps.

   

  0

Please sign in to leave a comment.