Vivotek Vortex Device Prerequisites & Installation Guide

Vivotek Vortex Device Prerequisites & Installation Guide

Vivotek Vortex Prerequisites & Installation Guide


VIVOTEK VORTEX is a cloud-based Video Management System (VMS) that enables secure device management, live video streaming, playback, event handling, and I/O control through APIs and web SDKs.

This documentation provides an end-to-end view of how VIVOTEK VORTEX devices are onboarded, configured, streamed, and controlled within the platform, and how external applications can integrate with VORTEX using REST APIs and the VORTEX Streaming SDK.

     Platform

1. Prerequisites  

Before proceeding, ensure the following:

  • A valid VIVOTEK VORTEX account.

  • Access to the VIVOTEK VORTEX Web Portal (Client Tool).

2. Authentication & Authorization

  • VORTEX APIs uses token-based authentication.

  • All API requests must include the required authorization headers.

 3. Device Onboarding & Configuration

  • Log in to the VIVOTEK VORTEX Web Portal

  • Navigate to My Account → API Key Management, and click Add option.

  •   To generate an API key and Keep it secure

  •   Navigate to the Device menu, then click the Add button to create a site.


  • Locate the HTTP Bearer authentication panel.

  • Enter your generated API key in the provided input field.

  • Click the SET button to apply the API key.

 


  • Navigate to the Groups → Get all groups section in the VORTEX Open API portal.

  • In this context, a Group represents a Site in the system.

  • Click the TRY button to execute the API request.

  • The API will return a list of all available sites (groups).

  • Each site includes a unique identifier called groupId.

  • Copy the required groupId from the response for use in  device discovery operations



  • Click the Add button to create a device.



 4.Live Streaming

  • Navigate to the View menu.

  • Confirm that the live video feed is working as expected.



5.VIVOTEK VORTEX Integration in genesis

 

  • Steps to add custom property:

    • Step 1: Login to genesis

    • Step 2: Navigate to configuration app

    • Step 3: At service provider level, click on edit button under overview tab

 

 

 

  • Step 4: Click on additional settings tab->Custom property

  • Step 5: Scroll down and click on the "Add +" button

 

  • Step 6: Enter parameter name and value as mentioned below

  • Add VivotekVortex device under the required site:

    • Navigate to the Configuration section in Genesis.

    • Navigate to DevicesAdd New Device:


  • Fill in the following details:

    • Device Name : e.g., "Vivotek Vortex Camera - Gate A"

    • Device Type : Vivotek Vortex

    • API Key : “Use the API Key that you created earlier”

    • External GroupID: “Use the Group ID (site) that you created earlier”

    • Event Call back implemented for events necessary webhook need to be created at device level.

    • cameraUniqueId: A unique value per camera or channel. Required for correct image fetch and archiving.

Click Save & Verify to confirm that the device is reachable and data (stream/events) is being received.

cameraUniqueId: A unique value per camera or channel. Required for correct image fetch.

  • Copy the device ID for use in event configuration

  • Navigate to Video Viewer.

 

 6.Events / Alarms (Webhook-Based Event Integration )

  • Events / Alarms Document URL: https://vivotek.zendesk.com/hc/en-001/articles/39346040829849--VORTEX-Portal-How-to-configure-webhook-in-alarm-management

  • This method uses Vivotek Vortex Webhooks, where the device actively sends events to our platform whenever an event occurs.

  • You need to configure the webhook URL in the device web interface, pointing to our service endpoint.

  • With the webhook feature in alarm management, you can configure automatic notifications to be sent to your specified URLs whenever a selected rule is triggered. This allows you to seamlessly integrate real-time alerts into your workflow or external systems.
     
    Setting Up a Webhook Profile in Alarm Management
    In the Alarm Management section, find and click the button to create a webhook profile.

    1. Webhook Name: Your preferred webhook name (eg.NXGEN Remote Video Monitoring)

    2. Integration URL: https://vivotekproxy.nxgen.cloud/EventIngest

    3. •SSL Handling: "Ignore SSL Certificate Errors" option is enabled

    4. Sending Method: By server

    5. Payload Type: JSON

Payload 
{
  "organizationName": "{{.OrganizationName}}",
  "organizationId": "{{.OrganizationId}}",
  "eventType": "{{.EventType}}",
  "eventName": "{{.EventName}}",
  "eventId": "{{.EventId}}",
  "deviceName": "{{.DeviceName}}",
  "deviceId": "{{.DeviceId}}",
  "mac": "{{.Mac}}",
  "deviceGroupName": "{{.DeviceGroupName}}",
  "deviceGroupId": "{{.DeviceGroupID}}",
  "localTime": {{.LocalTime}},
  "timezone": "{{.Timezone}}",
  "alarmId": "{{.AlarmId}}",
  "profileName": "{{.ProfileName}}",
  "imageFace": "{{.ImageFace}}",
  "imagePerson": "{{.ImagePerson}}", 
  "nxgenDeviceId": "Enter nxgen device id  that you created earlier",

               }

  • Note
    Currently, if you choose to send by cloud, IP address is not allowed for URL, use domain name instead.
    Don't use language other than English, as it can cause the webhook to fail.
    If the sending method is by device, make sure the receiving end and the device are on the same local network.


Below is the list of variables we have
Definition

Parameter

Description

EventId

Id of event that triggered

DeviceId

Id of the device that triggered the event

Mac

MAC address of the device that triggered the event

DeviceGroupID

Id of the Group of the device that triggered the event

EventName

Name of event that triggered

DeviceName

Name of the device that triggered the event

DeviceGroupName

Name of the Group of the device that triggered the event

OrganizationId

Organization Id from which webhook is created.

OrganizationName

Organization Name from which webhook is created.

LocalTime

Time at which event occurred. The time zone in which the cameras are physically located. It is in Unix timestamp format.

LocalISOTime

Time at which event occurred. The time zone in which the cameras are physically located. It is in ISO 8601 format.

UtcTime

UTC Time at which event occurred. It is in Unix timestamp format.

UtcISOTime

UTC Time at which event occurred. It is in ISO 8601 format.

Timezone

Timezone

EventType

Type of event that triggered. It is the event you see in alarm

management.

AlarmId

Unique ID sent through the configured alarm in Alarm Management

ProfileName

Display the name of the identified person if they are a known individual; otherwise, display 'Unknown'

ImagePerson

Full-body photo of the person who triggered the facial recognition;

The image is provided in base64 format

ImageFace

A facial photo of the person who triggered the facial recognition

The image is provided in base64 format.

Object

What triggered the detection, "human" or "vehicle"

Information

Displays whose configured condition was violated to trigger this event.

PersonId

Get the unique ID of the identified person

nxgenDeviceId

Enter the nxgen device ID

 

After the webhook profile is created, you can set webhook as an alarm action, and choose which profile you would like to apply.

 

Add an Alarm to Send Webhook
1. Select the ‘Add alarm’ icon in the top right.

123.png


2. Select which event types that will trigger webhooks.


圖片2.png

 
3. Select which device sources will trigger webhooks.

螢幕擷取畫面 2025-01-06 171519.png

圖片3.png

 

4. Select the webhook profile you created in the previous step.

螢幕擷取畫面 2025-01-06 171950.png

 
5. Set the schedule for sending this webhook.


螢幕擷取畫面 2025-01-06 180049.png

 6. Name this alarm and complete the setup.



螢幕擷取畫面 2025-01-06 180205.png

 

Navigate to the Message Center menu to check the generated events and alarms.

 

  • Navigate to Video Activity Search.

 

 

 

    • Related Articles

    • VIVOTEK On‑Premise (NVR)

      VIVOTEK On‑Premise (NVR) – Prerequisites & Installation Guide VIVOTEK On‑Premise (NVR) is a network video recorder that enables secure device management, live video streaming, playback, event handling, and I/O control through C# SDKs. This document ...
    • Maps guide

      GCXONE Maps Feature Guide Site Configuration & Operational Awareness 1. Overview The Maps feature in GCXONE provides a unified geospatial view of your entire security estate. Operators can visualise customers, sites, devices, cameras, and sensors on ...
    • Mobile App Guide

      BY NXGEN Mobile App GCXONE Mobile App Guide End User Guide 2026 Introduction The GCXONE mobile app gives you secure, on-the-go access to your security monitoring platform. From your smartphone you can view live camera feeds, check site and device ...
    • Geutebrueck Device Configuration

      Geutebrueck Device Configuration Platform Geutebrueck is VMS applications. It provides recording, live viewing, playback, events/alarms. Port Web API Interface: HTTPS 13333 RTSP Streaming: 554 Applications G-Set → system configuration G-View → ...
    • Tower Monitoring Alarm Configuration Guide (Includes Teltonika-IOT, EFOY and Victron Device Configuration)

      Introduction When we refer to Tower Monitoring in Genesis, we are describing an integrated ecosystem of multiple IoT subsystems working together to ensure the tower’s operational continuity, energy efficiency, and communication reliability. Each ...