Event streaming over WebSocket

Axis products generate events when they need to notify the client that a state change has occurred. Some examples include motion detection or I/O port state change. These events are used to trigger an action on the client’s side. The following examples will show you how to receive events over a WebSocket connection.

Establish WebSocket connection

GET /vapix/ws-data-stream?sources=events HTTP/1.1
Host: 192.168.0.90
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Authorization:
  Digest username="root" realm="AXIS_ACCC8EC43707",
  nonce="rMSij/TBQA=646b1c2c4c0a80a7feb4e34ef9e3422180924c37",
  uri="/vapix/ws-data-stream?sources=events",
  algorithm=MD5,
  response="683f06da91f927fa1772c42f16597"
Upgrade: websocket
Origin: chrome-extension://cbcbkhdmedgianpaifchdaddpnmgnknn
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: 1L91ICBqd8iwa0I0e6Wgzg==

HTTP/1.1 101 Switching Protocols
Date: Tue, 02 Nov 2021 16:09:47 GMT
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: kZ1kuOZMJmrfKnY8FvL7Tjwb0iw=
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits=15

HTTP/1.1 401 Unauthorized
Date: Tue, 02 Nov 2021 16:09:47 GMT
Server: Apache/2.4.48 (Unix) OpenSSL/1.1.1l
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
WWW-Authenticate:
  Digest realm="AXIS_ACCC8EC43707",
  nonce="5X26hdDPBQA=f1d9367d1b0699f406a95bbf79e35f6e08c5d3af",
  algorithm=MD5,
  stale=true,
  qop="auth"
Content-Length: 381
Content-Type: text/html; charset=iso-8859-1

Select events to receive

{
  "apiVersion": "1.0",
  "context": "Client defined request ID",
  "method": "events:configure",
  "params": {
    "eventFilterList": [
      {
        "topicFilter": "tns1:PTZController/tnsaxis:PTZReady"
      },
      {
        "contentFilter": "boolean(//SimpleItem[@Name=\"ready\" and @Value=\"1\"])"
      },
      {
        "topicFilter": "tns1:Device/tnsaxis:IO/VirtualInput",
        "contentFilter": "boolean(//SimpleItem[@Name=\"port\" and @Value=\"1\"]) and boolean(//SimpleItem[@Name=\"state\" and @Value=\"0\"])"
      }
    ]
  }
}

{
  "apiVersion": "1.0",
  "context": "Client defined request ID",
  "method": "events:configure",
  "data": {
  }
}

{
  "apiVersion": "1.0",
  "context": "Client defined request ID",
  "method": "events:configure",
  "error": {
    "code": 1100,
    "message": "Internal Error"
  }
}

Event streaming

{
  "apiVersion": "1.0",
  "method": "events:notify",
  "params": {
    "notification": {
      "timestamp": 1639385866198,
      "topic": "tns1:Device/tnsaxis:IO/VirtualPort",
      "message": {
        "source": {
          "port": "1"
        },
        "key": {},
        "data": {
          "state": "0"
        }
      }
    }
  }
}

This method should be used when you want to perform event streaming over a WebSocket using a common WebSocket endpoint. The endpoint location for data streaming is ws(s)://<device>/vapix/ws-data-stream and the WebSocket connection established on this endpoint can be used simultaneously with multiple data sources.

The data source that should be used is given as a parameter in the URL when the connection is established. Multiple data sources can be given as a comma-separated list. The URL ws(s)://<device>/vapix/ws-data-stream?sources=events should be used for the event streaming.

When a connection has been established, the client can send configuration requests in the JSON-RPC style defined in the following sections. Events streamed back to the client should use the same messaging style.

Authentication

The client need to authenticate itself before it can use the API. This can be done in one of two ways:

• Digest: Digest authentication can be achieved by following the standard Digest authentication process. When authentication is performed the connection will be upgraded to a WebSocket connection.

• Session token: Generate a session token and use it for authentication in cases where digest authentication isn’t supported. A session token is generated with a GET request to the URL http(s)://<device>/axis-cgi/wssession.cgi. This request itself require standard digest authentication to work. The device will respond with a session token that is valid for 15 seconds and will expire immediately when the time has passed. The token shall be used in the WebSocket connection URL as a parameter (wssession) ws(s)://<device>/vapix/ws-data-stream?wssession=<session-token>&sources=events, which can look like this: wss://<device>/vapix/ws-data-stream?wssession=1331901001644832701&sources=events

Please note that it is always recommended to use secure/encrypted connections with HTTPS and WSS protocols. Data transferred in clear format with HTTP and WS protocols are not secure.

This method should be used when you want to send a configuration request to the event data source.

Request

{
  "apiVersion": "<Major>.<Minor>",
  "context": <string>,
  "method": "events:configure",
  "params": {
    "eventFilterList": [
      {
        "topicFilter": <string>,
        "contentFilter": <string>
      },
      {
        "topicFilter": <string>,
        "contentFilter": <string>
      },
      {
        "topicFilter": <string>,
        "contentFilter": <string>
      }
    ]
  }
}

tns1:Device/tnsaxis:Status/SystemReady
tns1:Device/tnsaxis:IO//
tns1:RuleEngine/MotionRegionDetector/Motion|tns1:Device/axis:IO/VirtualPort
tnsaxis:CameraApplicationPlatform/VMD/Camera1ProfileANY

boolean(//SimpleItem[@Name="ready" and @Value="1"])
boolean(//SimpleItem[@Name="port" and @Value="1"]) and boolean(//SimpleItem[@Name="active" and @Value="0"])

Return value - Success

{
  "apiVersion": "<Major>.<Minor>",
  "context": <string>,
  "method": "events:configure",
  "data": {
  }
}

Return value - Failure

{
  "apiVersion": "<Major>.<Minor>",
  "context": <string>,
  "method": "events:configure",
  "error": {
    "code": <integer>,
    "message": <string>
  }
}

Error codes

See General error codes for a complete list of potential errors.

Events are sent to the client as JSON requests. The client should not respond to these notification requests.

{
  "apiVersion": "<Major>.<Minor>",
  "method": "events:notify",
  "params": {
    "notification": {
      "timestamp": <integer>,
      "topic": <string>,
      "message": {
        "source": {
          <string>: <string>,
          <string>: <string>
        }
        "key": {
          <string>: <string>,
          <string>: <string>
        },
        "data": {
          <string>: <string>,
          <string>: <string>
        }
      }
    }
  }
}

The following table consist of errors that may occur for any method. Errors specific to a method are listed under their separate API description. The error codes exist in the following ranges.

1100–1199

Generic error codes common for many APIs and reserved for server errors such as “Could not read configuration from file”. The actual cause can be seen in the server log and can sometimes be solved by restarting the device.

1200–1999

API-specific server errors that may collide between different APIs.

2100–2199

Generic error codes common to many APIs and reserved for client errors such as “Invalid parameter”. These errors should be possible to solve by changing the input data to the API.

2200–2999

API-specific client errors that may collide between different APIs.