Skip to main content

Content destination integration

A content destination receives recordings from an Axis body worn system (BWS). It can be an evidence management system (EMS), video management system (VMS), media server, or another application that you implement or integrate with.

Your application implements the body worn content destination API. The BWS is the client, and your application is the server.

How recording offload works​

Recordings move from a body worn camera to a docking station, then to the system controller. The system controller pushes content to your application over HTTPS. It buffers content until your application confirms the transfer, so recordings are retained when your application is temporarily unavailable.

A BWS needs one connected content destination. Administrators connect it by importing a connection file that your application generates in AXIS Body Worn Manager.

Build a content destination​

The body worn content destination API is based on a subset of the OpenStack Swift object storage API. Implement the API to:

  • Authenticate requests from the BWS.
  • Receive containers and objects for recordings and their associated data.
  • Publish the capabilities that your application supports.
  • Receive user and device information.

Your application receives video clips, recording metadata, and, when enabled, supplementary objects such as bookmarks, GNSS trails, signed video, and encryption keys. Use the API capabilities to declare which optional data your application supports.

For the endpoint definitions, connection-file format, object layout, and capability details, use the body worn content destination API specification and example server.

Protect recordings​

The BWS can encrypt video on the camera with a public key that you provide in the connection file. The system controller transfers the encrypted content without access to the corresponding private key. Your content destination uses the private key to decrypt the video.

The system also provides transfer status and user and device information for recording traceability. When configured, it can also provide signed video. See Export body worn recordings for guidance on processing the delivered content.

Next steps​