Reference · built on requestConnectorAccess control & video

Wisenet WAVE

Devices, event log, bookmarks, alarms, and video from Wisenet WAVE Servers through the /rest/v3 API and JSON-RPC subscriptions.

Request accessPricing ↗

About

Wisenet WAVE is video management software from Hanwha Vision. A WAVE System is one or more WAVE Servers holding Devices, Users, Layouts, Event Rules, Bookmarks, and recorded archive. Each Server answers an HTTP API: a RESTful /rest/v3 surface for reading and saving those entities, a JSON-RPC endpoint at /jsonrpc for batches and change subscriptions, and stream URLs for live or recorded video. A System connected to WAVE Sync can be reached through the Cloud proxy.

Through Fibric, an operator reads Device status, the Event Log, and Metrics alarms, then proposes a bookmark, a Generic Event, or a PTZ preset for your approval. The connector makes the call once and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Wisenet WAVE and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Device records and per-Device diagnosis from GET /rest/v3/devices and GET /rest/v3/devices/*/status
  • Server records, runtime info, storages, and recording statistics under /rest/v3/servers
  • The Event Log per Server from GET /rest/v3/servers/{serverId}/events, filterable by event type, rule, resource, text, and time
  • Bookmarks and recorded-footage chunks from /rest/v3/devices/{deviceId}/bookmarks and /rest/v3/devices/{id}/footage
  • Thumbnails from GET /rest/v3/devices/{id}/image and live or archive streams from /rest/v3/devices/{id}/media.{format} in webm, mpegts, mp4, or mkv
  • Active Metrics alarms and current values from /rest/v3/system/metrics/alarms and /rest/v3/system/metrics/values
  • Object changes pushed over the JSON-RPC WebSocket at /jsonrpc after a .subscribe request such as rest.v3.devices.subscribe

Proposed actions

  • Target capability: propose a Bookmark on a Device through POST /rest/v3/devices/{deviceId}/bookmarks with name, description, start time, duration, and tags
  • Target capability: propose a Generic Event through POST /api/createEvent with source, caption, description, and cameraRefs, handled by the current Event Rules
  • Target capability: propose activating a saved PTZ preset through POST /rest/v3/devices/{deviceId}/ptz/presets/{id}/activate
  • Target capability: propose a new or changed Event Rule through /rest/v3/events/rules, which works with the new Event Rule Engine only

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Catch a camera that stopped recording

    GET /rest/v3/devices/*/status returns each Device's diagnosis and /rest/v3/devices/{id}/footage shows gaps in recorded chunks. The operator proposes a ticket with the last thumbnail attached.

    With Camera Health

  • Bookmark the footage behind an incident

    An alarm arrives from another system. The operator finds the Devices covering that location and proposes a Bookmark with start time, duration, and tags so the clip is findable later.

    With Incident Draft, Audit Trail

  • Turn a Metrics alarm into a triaged task

    Active alarms from /rest/v3/system/metrics/alarms cover storage, servers, and cameras. The operator groups them by Server, ranks them, and proposes who should look first.

    With Alarm Triage

  • Review a suspected tailgate on video

    A door controller reports two entries on one badge. The operator pulls thumbnails from the camera at that door for the window and proposes a Bookmark for review.

    With Tailgate Review

Requirements

  • A WAVE Server reachable over HTTPS from the connector, or a System connected to WAVE Sync so calls route through the Cloud proxy
  • A local, LDAP, or Cloud user whose permissions cover the Devices, Servers, and Event Rules you want read or changed
  • VMS 6.0 or later for /rest/v3; 5.1 for /rest/v2; 5.0 for /rest/v1. GET /rest/v3/system/info reports restApiVersions
  • The new Event Rule Engine on the System if rules are to be created through /rest/v3/events/rules
Authentication
A session token from POST /rest/v3/login/sessions for a local or LDAP user, sent as an HTTP Bearer header over HTTPS; Cloud users obtain their token from the Cloud by OAuth2.

Limits

  • Administrator functions under /rest require a fresh session token confirmed by the administrator's password
  • HTTP Basic, Digest, and URL-based authentication are deprecated, off unless an admin enables them per user, and rejected by new admin functions
  • LEGACY & BETA functions such as /api/createEvent and the Transaction Bus can change without notice; the vendor points to /rest and /jsonrpc where equivalents exist
  • Streams may be transcoded by the Server on the fly. This listing pulls thumbnails and clips on demand; it does not consume continuous video

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Wisenet WAVE ↗

Questions and answers

Which WAVE API version should an integration use?
The vendor's advice is the newest REST version of the lowest VMS version you intend to support: /rest/v1 for 5.0 and later, /rest/v2 for 5.1 and later, /rest/v3 for 6.0 and later. GET /rest/v3/system/info lists a Server's restApiVersions.
How does WAVE push changes without polling?
Over the JSON-RPC WebSocket at /jsonrpc. Send a .subscribe request where you would send .get, and the Server sends .update notifications on each System database change for that entity. The older Transaction Bus at /ec2/transactionBus/websocket still exists and is marked use at your own risk.
Can an outside system raise an event inside WAVE?
Yes. POST /api/createEvent triggers a Generic Event with source, caption, description, and optional cameraRefs, handled by the current Event Rules. POST /rest/v3/events/send takes a ruleId and props. Rules can then activate I/O, run a PTZ preset, open an alarm layout, create a bookmark, or send an HTTP request to another system.
Ask about Wisenet WAVE

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Wisenet WAVE through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy