Hik Ipmd V2.0 201404

IP Media Device Management Protocol
User Guide
Version 2.0
Revision 2.0
2014-04
http://www.hikvision.com/
COPYRIGHT 2009, Hikvision Digital Technology Co., Ltd
Revision
History
Description
Date
Version 1.0
Revision 1
Initial version
Version 1.0
Revision 2
Finished the Mandatory services
Version 1.0
Revision 3
Version 1.0
Revision 4
2009-6
2009-8
Corrections,
expanded services
Corrections, updates services and resources
2009-10
2009-11
Version 1.0
Revision 5
Protocol revision
Verison 1.0
Revision 5.1
Corrections,
resources
Verison 1.0
Revision 5.2
Update the /PTZ/channels/ID/PTZControl resources
Verison 1.0
Revision 5.3
Amend the DDNS related resources; add the

/Security/adminAccess resources
2010-02
Verison 1.0
Revision 5.4
The <Zeroconf> tag is supported in the block XML of

/System/Network/interfaces
/ID/discovery.
Add the /System/logging
The <pulseDuration> tag is supported in the block
XML of IO/outputs/ID.
The <pulseDuration> tag is not supported in the block
XML of /IO/outputs/ID/trigger.
Modify some parameter values in Audio Service.
The <enabled> can be configured in the <Audio> of
the block XML /Streaming
/channels/ID
2010-04
Verison 1.0
Revision 5.5
<videoResolution>
is
<videoResolutionWidth> and
<videoResolutionHeight> in the
/Streaming/channels/ID
2010-05
Verison 1.0
Revision 5.6
Redefine
the
mean
of
ID
in
the
URI :/Event/triggers/ID/notifications/ID , it just a
sequence number of a trigger or a notification .
2010-06
Verison 1.0
Revision 5.7
Add resourceCustom/HIKCGI/Event/ schedule/ ID.

The<dynamicIP>tag is supported in the block XML of
/Network/interfaces/ID/ pppoe
2010-09
Verison 1.0
New resource /System/Storage is defined
2011-01
amend
2009 2014 by HIKVISION. All rights reserved.
2009-12
PTZ
service
replaced
and
2010-01
2010-01
with
Revision 5.8
New service /PTZCtrl is defined

New service /Image is defined
New service /Record is defined
Service is Custom/HIKCGI/Event/ schedule/ ID is
redefined to: /Event/schedule/ ID.
New service /Network/interfaces/ID/Adapter is
defined
Service /Event/notification/mailing/ID
definition is updated , to support multi email receivers
New service
/Image/channels/<ID>/NosiseReduceExt is defined
New service /Image/channels/<ID>/Scene is
defined
New service /Image/channels/<ID>/EPTZ is defined
New service /Image/channels/<ID>/PTZ is defined
New service /Image/channels/<ID>/EIS is defined
Verison 1.0
Revision 5.9
Service /Image/channels/<ID>/IrcutFilter has been

replaced by
/Image/channels/<ID>/IrcutFilterExt,and the
IrcutFilterTime cant meet the need of setting
in both directions.It needs to explain the unit of time in
notes.
Service /Image/channels/<ID>/WDR has been
replaced by /Image/channels/<ID>/WDRExt. The
new service adopt <mode> tag, support a level, and
can by extended by other level.
Comments were added on the service
/Image/channels/<ID>/HLC.
All sub-branches were list in the service
/Image/channels
Added Id to the NFS xml block.
2012-03
Added <exposureMode> tag and <WDREnabled> tag

to the service video,
PTZ were extended to HIKCGI.
Added FTPHTTP and PTZ to Linking Method.
Added <enabled> tag, <privacymaskName> tag and
<maskType> tag to service
/Video/inputs/channels/ID/privacyMask/regions/ID
Service /System/Storage/volumes/ID/URL was
revised as
/System/Storage/volumes/ID/Format
IR was reached agreement.
No index was used in tag <ZoomLimitRatio>.
The new <mode> tag in service
/Image/channels/<ID>/WDRExt was optional.
Add MULTI-AREA option to the tag <BLCMode> in
service /Image/channels/<ID>/BLS.
New service /Image/channels/<ID>/HLC is defined.
New service
/Image/channels/<ID>/ChromaSuppress is
defined.
New service /Image/channels/<ID>/ZoomLimit is
defined.
New service /Image/channels/<ID>/ExpComp is
defined.
Delete
/PSIA/Custom/HIK/PTZ/channels/ID/patterns,
/PSIA/Custom/HIK/PTZ/channels/ID/ptzlimiteds,
and /PSIA/Custom/HIK/PTZ/channels/ID/timetasks
in PTZ.
Verison 2.0
New service /Smart branch is defined
2013-11
Revision 1.0
New service
/Streaming/channels/<ID>/dynamicCap is defined.
The new <SVC> tag in service
/Streaming/channels/<ID> is optional.
Added <panSupport> tag, <tiltSupport> tag and
<zoomSupport> tag to service
/Streaming/channels/<ID> was optional.
New service /MotionDetectionExt/<ID> is defined
New service /MotionDetectionExt/<ID>/switch is
defined
New service /MotionDetectionExt/<ID>/regions is
defined
New service
/MotionDetectionExt/<ID>/regions/<ID> is defined
New service
/PTZCtrl/channels/<ID>/onepushfoucs/start is
defined.
New service
/PTZCtrl/channels/<ID>/onepushfoucs/reset is
defined.
New service /PTZCtrl/channels/<ID>/position3D is
defined.
Verison 2.0
Revision 2.0
Update the /System/fisheye resources
http://www.hikvision.com/
COPYRIGHT, Hikvision Digital Technology Co., Ltd

2014-04
Notices
The information in this documentation is subject to change without notice and does not
represent any commitment on behalf of HIKVISION. HIKVISION disclaims any liability
whatsoever for incorrect data that may appear in this documentation. The product(s) described
in this documentation are furnished subject to a license and may only be used in accordance
with the terms and conditions of such license.
Copyright 2009-2014 by HIKVISION. All rights reserved. This documentation is issued in
strict confidence and is to be used only for the purposes for which it is supplied. It may
not be reproduced in whole or in part, in any form, or by any means or be used for any other
purpose without prior written consent of HIKVISION and then only on the condition that this
notice is included in any such reproduction. No information as to the contents or subject matter
of this documentation, or any part thereof, or arising directly or indirectly therefrom, shall be
given orally or in writing or shall be communicated in any manner whatsoever to any third party
being an individual, firm, or company or any employee thereof without the prior written consent
of HIKVISION. Use of this product is subject to acceptance of the HIKVISION agreement
required to use this product. HIKVISION reserves the right to make changes to its products as
circumstances may warrant, without notice.
This documentation is provided as-is, without warranty of any kind. Please send any
comments regarding the documentation to:
[email protected]
Find out more about HIKVISION at www.hikvision.com
Contents
1
2
3
3.1
3.2
4
4.1
4.2
4.3
4.4
4.5
4.6
4.7
5
6
6.1
6.2
6.3
7
7.1
7.2
7.3
7.4
8
8.1
Scope ............................................................................................................................... 1
References ...................................................................................................................... 1
Definitions and abbreviations ....................................................................................... 2
Definitions......................................................................................................................... 2
Abbreviations .................................................................................................................... 2
Architecture and Transmission Mechanism................................................................ 2
REST and HTTP Methods ................................................................................................ 3
XML.................................................................................................................................. 3
Resources overview .......................................................................................................... 4
Protocol URL .................................................................................................................... 5
Messages ........................................................................................................................... 6
4.5.1
Connection Header Field............................................................................... 6
4.5.2
Authorization and WWW-Authenticate Header Fields .............................. 6
4.5.3
Entity Body ...................................................................................................... 6
4.5.4
Operations ....................................................................................................... 7
4.5.5
Error Handling ................................................................................................. 8
Namespaces..................................................................................................................... 13
Security ........................................................................................................................... 13
Device discovery .......................................................................................................... 13
Resource Description .................................................................................................. 14
Resource Description Outline ......................................................................................... 14
Built-in Types .................................................................................................................. 15
Annotation....................................................................................................................... 16
Special Resources........................................................................................................ 16
index ................................................................................................................................ 16
indexr .............................................................................................................................. 17
description ....................................................................................................................... 17
capabilities ...................................................................................................................... 17
Services and General Resources .............................................................................. 20
System ............................................................................................................................. 20
8.1.1
Device Information ....................................................................................... 20
8.1.2
Configuration file(s) ...................................................................................... 21
8.1.3
Factory default .............................................................................................. 22
8.1.4
Firmware upgrade ........................................................................................ 22
8.1.5
Reboot ............................................................................................................ 22
8.1.6
Status.............................................................................................................. 23
8.1.7
Time ................................................................................................................ 23
8.1.8
LocalTime ...................................................................................................... 24
8.1.9
TimeZone ....................................................................................................... 24
8.1.10 NtpServers ..................................................................................................... 25
8.1.11 NtpServer ....................................................................................................... 26
8.1.12 Log .................................................................................................................. 27
I
8.2
8.3
8.4
8.5
8.6
8.1.13 Storage ........................................................................................................... 29

8.1.14 FishEye .......................................................................................................... 32
Network........................................................................................................................... 32
8.2.1
Interfaces ....................................................................................................... 32
8.2.2
Interface ......................................................................................................... 33
8.2.3
IPAddress....................................................................................................... 33
8.2.4
Wireless ......................................................................................................... 34
8.2.5
DetectedWirelessList ................................................................................... 36
8.2.6
DetectedWireless ......................................................................................... 36
8.2.7
Discovery ....................................................................................................... 37
8.2.8
PPPoE ............................................................................................................ 37
8.2.9
DDNS ............................................................................................................. 38
8.2.10 NFSList .......................................................................................................... 39
8.2.11 NFS ................................................................................................................. 39
8.2.12 Adapter ........................................................................................................... 40
8.2.13 Examples ....................................................................................................... 41
IO .................................................................................................................................... 43
8.3.1
Status.............................................................................................................. 43
8.3.2
Inputs .............................................................................................................. 44
8.3.3
Input ................................................................................................................ 44
8.3.4
Input status .................................................................................................... 45
8.3.5
Outputs ........................................................................................................... 45
8.3.6
Output ............................................................................................................. 46
8.3.7
Output status ................................................................................................. 46
8.3.8
Output trigger ................................................................................................ 47
Video ............................................................................................................................... 47
8.4.1
Input ................................................................................................................ 47
8.4.2
Input channels ............................................................................................... 48
8.4.3
Input channel ................................................................................................. 48
8.4.4
Input channel overlay texts ......................................................................... 49
8.4.5
Input channel overlay text ........................................................................... 50
8.4.6
Input channel channelNameOverlay ......................................................... 51
8.4.7
Input channel privacyMask.......................................................................... 52
8.4.8
Input channel privacyMask regions ........................................................... 52
8.4.9
Input channel privacyMask region ............................................................. 53
8.4.10 Input channel shelterAlarm ......................................................................... 55
8.4.11 Input channel shelterAlarm regions ........................................................... 56
8.4.12 Input channel shelterAlarm region ............................................................. 57
8.4.13 Input channel osdDatetime ......................................................................... 58
Audio............................................................................................................................... 58
8.5.1
Channels ........................................................................................................ 59
8.5.2
Channel .......................................................................................................... 59
Two way audio ................................................................................................................ 60
8.6.1
Open ............................................................................................................... 60
II
8.7
8.8
8.9
8.10
8.11
8.6.2
Close .............................................................................................................. 60
8.6.3
Send data....................................................................................................... 61
8.6.4
Receive data ................................................................................................. 61
Serial ............................................................................................................................... 62
8.7.1
Ports ............................................................................................................... 62
8.7.2
Port ................................................................................................................. 62
8.7.3 Command ............................................................................................................ 63
8.7.3
Transparent channel open .......................................................................... 64
8.7.4
Transparent channel close .......................................................................... 64
8.7.5
Transparent channel send data .................................................................. 64
8.7.6
Transparent channel receive data.............................................................. 65
Security ........................................................................................................................... 65
8.8.1
Users .............................................................................................................. 65
8.8.2
User ................................................................................................................ 66
8.8.3
adminAccess ................................................................................................. 67
Streaming ........................................................................................................................ 68
8.9.1
Status.............................................................................................................. 68
8.9.2
Channels ........................................................................................................ 68
8.9.3
Channel .......................................................................................................... 69
8.9.4
Dynamic capabilities .................................................................................... 75
8.9.5
Channel status .............................................................................................. 76
8.9.6
Picture ............................................................................................................ 77
8.9.7
Request keyframe ........................................................................................ 77
Motion Detection ............................................................................................................ 78
8.10.1 One channel motion detection .................................................................... 78
8.10.2 Motion detection regions ............................................................................. 79
8.10.3 Motion detection region ............................................................................... 80
8.10.4 Motion Detection Example .......................................................................... 81
8.10.5 /MotionDetectionExt/<ID> ........................................................................... 84
8.10.6 /MotionDetectionExt/<ID>/switch ............................................................... 85
8.10.7 /MotionDetectionExt/<ID>/regions ............................................................. 86
8.10.8 /MotionDetectionExt/<ID>/regions/<ID> ................................................... 86
Event ............................................................................................................................... 88
8.11.1 Triggers .......................................................................................................... 88
8.11.2 Trigger ............................................................................................................ 89
8.11.3 Trigger notifications ...................................................................................... 90
8.11.4 Trigger notification ........................................................................................ 91
8.11.5 Schedule ........................................................................................................ 93
8.11.6 Schedule/ID ................................................................................................... 93
8.11.7 Notification ..................................................................................................... 95
8.11.8 Mails notification ........................................................................................... 95
8.11.9 Mail notification ............................................................................................. 96
8.11.10 HTTP Hosts ................................................................................................... 98
8.11.11 HTTP Host ..................................................................................................... 98
III
8.12
8.13
8.11.12 Notification alertStream ............................................................................... 99

8.11.13 Event Triggering Examples ....................................................................... 101
PTZ ............................................................................................................................... 102
8.12.1 Channels ...................................................................................................... 102
8.12.2 Channel ........................................................................................................ 103
8.12.3 Patrols .......................................................................................................... 105
8.12.4 Patrol ............................................................................................................ 105
8.12.5 Patrol keyPoints .......................................................................................... 106
8.12.6 Patrol keyPoint ............................................................................................ 106
8.12.7 PTZControl .................................................................................................. 107
PTZCtrl ......................................................................................................................... 109
8.13.1 /PTZCtrl/channels ....................................................................................... 109
8.13.2 /PTZCtrl/channels/<ID> ............................................................................. 110
8.13.3 /PTZCtrl/channels/<ID>/homeposition .................................................... 111
8.13.4 /PTZCtrl/channels/<ID>/homeposition/goto ........................................... 112
8.13.5 /PTZCtrl/channels/<ID>/continuous ......................................................... 112
8.13.6 /PTZCtrl/channels/<ID>/momentary ........................................................ 113
8.13.7 /PTZCtrl/channels/<ID>/relative ............................................................... 113
8.13.8 /PTZCtrl/channels/<ID>/absolute ............................................................. 114
8.13.9 /PTZCtrl/channels/<ID>/digital.................................................................. 114
8.13.10 /PTZCtrl/channels/<ID>/status ................................................................. 115
8.13.11 /PTZCtrl/channels/<ID>/presets ............................................................... 115
8.13.12 /PTZCtrl/channels/<ID>/presets/<ID> ..................................................... 116
8.13.13 /PTZCtrl/channels/<ID>/presets/<ID>/goto ............................................ 117
8.13.14 /PTZCtrl/channels/<ID>/patrols ................................................................ 117
8.13.15 /PTZCtrl/channels/<ID>/patrols/<ID> ...................................................... 118
8.13.16 /PTZCtrl/channels/<ID>/patrols/<ID>/start.............................................. 119
8.13.17 /PTZCtrl/channels/<ID>/patrols/<ID>/stop .............................................. 120
8.13.18 /PTZCtrl/channels/<ID>/patrols/<ID>/pause .......................................... 120
8.13.19 /PTZCtrl/channels/<ID>/patrols/<ID>/status........................................... 120
8.13.20 /PTZCtrl/channels/<ID>/patrols/<ID>/schedule ..................................... 121
8.13.21 /PTZCtrl/channels/<ID>/patterns.............................................................. 121
8.13.22 /PTZCtrl/channels/<ID>/patterns/<ID> .................................................... 122
8.13.23 /PTZCtrl/channels/<ID>/patterns/<ID>/recordstart ................................ 123
8.13.24 /PTZCtrl/channels/<ID>/patterns/<ID>/recordstop ................................ 123
8.13.25 /PTZCtrl/channels/<ID>/patterns/<ID>/run ............................................. 123
8.13.26 /PTZCtrl/channels/<ID>/patterns/<ID>/stop ........................................... 124
8.13.27 /PTZCtrl/channels/<ID>/PTZOSDDisplay ............................................... 124
8.13.28 /PTZCtrl/channels/<ID>/parkaction .......................................................... 125
8.13.29 /PTZCtrl/channels/<ID>/ptzlimiteds ......................................................... 125
8.13.30 /PTZCtrl/channels/<ID>/ptzlimiteds/<ID> ............................................... 126
8.13.31 /PTZCtrl/channels/<ID>/ptzlimiteds/<ID>/setstart ................................. 127
8.13.32 /PTZCtrl/channels/<ID>/ptzlimiteds/<ID>/set ......................................... 127
8.13.33 /PTZCtrl/channels/<ID>/saveptzpoweroff ............................................... 127
IV
8.14
8.13.34 /PTZCtrl/channels/<ID>/timetasks ........................................................... 128

8.13.35 /PTZCtrl/channels/<ID>/timetasks/<ID> ................................................. 129
8.13.36 /PTZCtrl/channels/<ID>/timetasks /<ID>/copytask ................................ 130
8.13.37 /PTZCtrl/channels/<ID>/auxcontrol.......................................................... 131
8.13.38 /PTZCtrl/channels/<ID>/onepushfoucs/start .......................................... 132
8.13.39 /PTZCtrl/channels/<ID>/onepushfoucs/reset ......................................... 132
8.13.40 /PTZCtrl/channels/<ID>/position3D ......................................................... 132
Image............................................................................................................................. 133
8.14.1 /Image/channels ......................................................................................... 133
8.14.2 /Image/channels/<ID> ................................................................................ 133
8.14.3 /Image/channels/<ID>/resetImage ........................................................... 135
8.14.4 /Image/channels/<ID>/restoreImageparam ............................................ 135
8.14.5 /Image/channels/<ID>/Focus .................................................................... 135
8.14.6 /Image/channels/<ID>/LensInitialization ................................................. 136
8.14.7 /Image/channels/<ID>/ImageFlip ............................................................. 137
8.14.8 /Image/channels/<ID>/ImageFreeze ....................................................... 137
8.14.9 /Image/channels/<ID>/proportionalpan ................................................... 138
8.14.10 /Image/channels/<ID>/WDRExt ............................................................... 138
8.14.11 /Image/channels/<ID>/BLC ....................................................................... 139
8.14.12 /Image/channels/<ID>/Imageenhancement ........................................... 140
8.14.13 /Image/channels/<ID>/IrcutFilterExt ........................................................ 141
8.14.14 /Image/channels/<ID>/NoiseReduceExt ................................................. 142
8.14.15 /Image/channels/<ID>/DSS ...................................................................... 143
8.14.16 /Image/channels/<ID>/WhiteBlance ........................................................ 143
8.14.17 /Image/channels/<ID>/Exposure .............................................................. 144
8.14.18 /Image/channels/<ID>/Sharpness............................................................ 144
8.14.19 /Image/channels/<ID>/Iris ......................................................................... 145
8.14.20 /Image/channels/<ID>/Shutter .................................................................. 146
8.14.21 /Image/channeles/<ID>/Gain .................................................................... 146
8.14.22 /Image/channeles/<ID>/GamaCorrection ............................................... 147
8.14.23 /Image/channels/<ID>/powerLineFrequency ......................................... 148
8.14.24 /Image/channels/<ID>/Color ..................................................................... 148
8.14.25 /Image/channels/<ID>/Scene ................................................................... 149
8.14.26 /Image/channels/<ID>/EPTZ .................................................................... 149
8.14.27 /Image/channels/<ID>/PTZ ....................................................................... 150
8.14.28 /Image/channels/<ID>/EIS ........................................................................ 150
8.14.29 /Image/channels/<ID>/HLC ....................................................................... 151
8.14.30 /Image/channels/<ID>/ChromaSuppress................................................ 152
8.14.31 /Image/channels/<ID>/ZoomLimit ............................................................ 152
8.14.32 /Image/channels/<ID>/ExpComp ............................................................. 153
8.14.33 /Image/channels/<ID>/IrLight.................................................................... 153
8.14.34 /Image/channels/<ID>/WDR(1.5.8 old version) ..................................... 154
8.14.35 /Image/channels/<ID>/NoiseReduce(1.5.8 old version) ....................... 155
8.14.36 /Image/channels/<ID>/IrcutFilter(1.5.8 old version) .............................. 155
V
8.15
Record ........................................................................................................................... 156

8.15.1 /Record/Schedule ....................................................................................... 156
8.16 Smart ............................................................................................................................. 157
8.16.1 /Smart/Capabilities ..................................................................................... 157
8.16.2 /Smart/ROI/channels/ID............................................................................. 158
8.16.3 /Smart/ROI/channels/<ID>/regions .......................................................... 159
8.16.4 /Smart/ROI/channels/<ID>/regions/<ID> ................................................ 159
8.16.5 /Smart/ROI/channels/<ID>/facetrace....................................................... 160
8.16.6 /Smart/ROI/channels/<ID>/objecttrace ................................................... 161
8.16.7 /Smart/FaceDetect/<ID> ............................................................................ 161
8.16.8 /Smart/IntelliTrace/<ID> ............................................................................. 162
8.16.9 /Smart/IntelliTrace/<ID>/ZoomRatial ....................................................... 163
8.16.10 /Smart/FieldDetection/<ID> ....................................................................... 163
8.16.11 /Smart/FieldDetection/<ID>/regions......................................................... 164
8.16.12 /Smart/FieldDetection/<ID>/regions/<ID> ............................................... 165
8.16.13 /Smart/DefocusDetection/<ID> ................................................................. 166
8.16.14 /Smart/AudioDetection/channels/<ID> .................................................... 167
8.16.15 /Smart/AudioDetection/channels/<ID>/Status ........................................ 167
8.16.16 /Smart/SceneChangeDetection/<ID> ...................................................... 168
Annex A (normative):.................................................................................................................. 169
A.0 hik.xsd ................................................................................................................................ 169
Annex B (Additional content for Encoder) ................................................................................... 172
Port ............................................................................................................................................ 172
/Streaming/channels/ID ............................................................................................................. 173
Motion Detection Region .......................................................................................................... 175
Trigger....................................................................................................................................... 175
Trigger notification ................................................................................................................... 176
Schedule/ID............................................................................................................................... 177
/PTZ/channels/ID ...................................................................................................................... 177
/Audio/channels/ID ................................................................................................................... 178
/Image/channels/<ID>............................................................................................................... 179
VI
1 Scope
This specification defines a HTTP-based application programming interface that enables
physical security and video management systems to communicate with IP media devices
in a particular way.
With regard to Media Streaming, please refer to develop API of RTSP protocol.
2 References
The following documents contain provisions which, through reference in this text,
constitute provisions of the present document.
References are either specific (identified by date of publication, edition number,

version number, etc.) or non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies.

[1]
[2]
[3]
[4]
[5]
[6]
[7]
[8]
RFC2616 Hypertext Transfer Protocol-HTTP/1.1

W3C XML 1.0 specification
W3C Character encodings
RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax and Semantics
RFC 2617 HTTP Authentication:Basic and Digest Access Authentication
International Electrotechnical Commission ISO/IEC standard on UPnP device
architecture makes networking simple and easy, 2008-12-09. Retrieved on
2009-05-07.
International Organization for Standardization ISO/IEC standard on UPnP
device architecture makes networking simple and easy, 2008-12-10. Retrieved
on 2009-05-07.
UPnP Forum UPnP Specifications Named International Standard for Device
Interoperability for IP-based Network Devices, 2009-02-05. Retrieved on
2009-05-07.
3 Definitions and abbreviations

3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Special Resources: index, indexr, description and capabilities resources, that are
contained in all Services and General Resources, and provide a special description for
these resources.
Services: a set of resources consisting of relevant General Resources.
General Resources: physical resources that supported by the devices.
Node: Services and General Resources.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
FQDN
REST
IO
UPnP
Fully Qualified Domain Name

REpresentational State Transfer
Input/Output
Universal Plug and Play
4 Architecture
and
Transmission
Mechanism
The IP Media Device Management Protocol is based on REST architecture. The
management and control interfaces defined in this specification are treated as resources
utilizing the REpresentational State Transfer (REST) architecture. This architecture
facilitates users by grouping related resources within hierarchical namespaces, and is
more flexible for service discovery and future expansion.
REST architecture consists of clients and servers, among which clients initiate request to
servers, while servers handle requests and response accordingly. Requests and
responses are established via the transmission of representations of resources. REST
architecture need to be based on an Application Layer protocol which provides various of
standard communication formats for applications based on the transfer of meaningful
representational state. HTTP[1] has a very rich vocabulary in terms of verbs(or methods),
URIs, request and response headers, Internet media types, HTTP request and response
codes etc. In addition, HTTP also has some features particularly suitable for REST
architecture. So HTTP is used as external Application Layer protocol in this specification.
In the architecture, clients are physical security and video management systems; servers
are IP media devices.
This specification also contains full XML schema for the introduced resources.
4.1 REST and HTTP Methods

The following table shows how HTTP verbs are typically used to implement a web service
based on REST architecture.
Table 1
Resource
GET
PUT
POST
DELETE
Collection URI, such as

http://webServer/resour
ces
List
the
members
of
collection,
complete with
their member
URIs
for
further
navigation.
Meaning
defined
as replace the
entire
collection
with
another
collection.
Create a new
entry
in
the
collection where
the ID is assigned
automatically by
the collection. The
ID
created
is
usually included
as part of the data
returned by this
operation.
Meaning
defined
as delete
the entire
collection
.
Member URI, such as

http://webServer/resour
ces/7416
Retrieve
a
representation
of
the
addressed
member of the
collection
expressed in
an appropriate
MIME type.
Update
the
addressed member
of the collection or
create it with the
specified ID.
Treat
the
addressed
member as a
collection in its
own right and
create a new
subordinate of it.
Delete
the
addresse
d member
of
the
collection.
4.2 XML
A device must support the syntax defined by W3C XML 1.0 specification [2] and UTF-8
character set [3]. All XML files must adopt UTF-8 encoding according to RFC3629.
Additionally, all resources share a common XML schema as defined in Annex.
Any resources can specify separate input and output XML Documents. If a specific data
structure is defined inside these documents, then they must be specified as XML Schema
Documents (xsd) in Annex.
Lists contained in XML blocks will be represented in the format of <XXXList>, and each
<XXXList> tag may contain one or more nodes.
4.3 Resources overview

Three kinds of resources are defined in this specification. They are Special Resources,
Services and General Resources. Related General Resources are grouped by
Services. Services and General Resources contain Special Resources. Figure 1 shows
their relationship.
Services
General Resources
Special Resources
Special Resources
Figure 1
The index, indexr, description and capabilities are defined as Special Resources in
this specification. Both index and description will be mandatorily included by each node,
and both indexr and capabilities will be optionally included by each node. For more
detailed description see Section 6.
Services defined in this specification are divided into different services categories. Each
category has its own name spaces (see Section 4.6 for the name space definitions). The
following services are defined:
Table 2
Services
Description
System
Configure and operate the general system

functions.
8.1
Network
Configure network interfaces.
8.2
Configure the Input/Output (IO).
8.3
Video
Handle video-related configuration.
8.4
Audio
Configure the Audio.
8.5
Control two ways audio.
8.6
Configure and control the Serial ports.
8.7
IO
Two way audio

Serial
Reference
Services
Security
Description
Reference
Provide Security functions.
8.8
Streaming
Configure and control the streaming media

content.
8.9
Motion Detection
Configure and control the motion detection of the

device
8.10
Event
Provide event notification functions.
8.11
PTZ
Control the device pan tilt and zoom.
8.12
Configure and control PTZ.
8.13
Image
Configure front-end parameters.
8.14
Record
Configure recording schedule.
8.16
Smart
Configure smart event parameters.
8.16
PTZCtrl
4.4 Protocol URL

The URL scheme is used to locate device resources via a specific protocol in the network.
This section defines the syntax and semantics for http(s) URLs.
<protocol>://<host>[:port][abs_path [?query]]
protocol: URL scheme for the particular request. The http and https protocols are allowed
in this specification.
host: The host field refer to the hostname, IP address, or the FQDN of an IP device.
port: The port field refer to the port number of that host on which the identified resource is
located at the IP device listening for TCP connections. If the port is empty or not given, the
default port is assumed. For HTTP, the default port 80. For HTTPS, the default port 443.
abs_path: The Request-URI [1] for the resources is abs_path [4]. The abs_path in this
specification is most often of the form [/Services][/General Resources][/Special
Resources], which is suitable for resources to update or restore device configurations.
ID which appears in the abs_path identifies one resource of a list resource in this
specification.
query: The query field is a string of information to be interpreted by the resource. It can
include some resource-related parameters. It must be listed in name-value pair syntax
(p1=v1&p2=v2&&pn=vn). Each resource can define a set of parameters. Defining input
data which is specific to the resource will be prior than query usage.
4.5 Messages
HTTP messages are used for communication between physical security and video
management systems and IP media devices in this specification. In order to configure and
control the device, some provisions are specified for these HTTP message.
4.5.1Connection Header Field

Devices that implement HTTP/1.1 should support persistent connections in order to meet
video management systems or client applications requirements that issue multiple
HTTP(s) transactions. HTTP/1.1 is implemented and utilized according to RFC 2616 in
the IP devices. For a video management system or client application that uses persistent
connection for multiple transactions, it is required to implement Connection: Keep-Alive
HTTP header field, while also adopt the Connection: close HTTP header field for the last
transaction of the persistent connection. This process will assume that the application can
identify the last request in a sequence of multiple requests.
4.5.2Authorization and WWW-Authenticate Header

Fields
When a video management system or client application sends any request to the device,
it must be authenticated by means of Basic Access [5] according to RFC 2617, and thus
all the devices are required to support Basic Access. Authorization header field is sent
along with each request, and if a user is authenticated, the request will follow the normal
execution flow. If client HTTP request is with no authentication credentials, unauthorized
HTTP response (401) will be returned with WWW-Authenticate header field.
4.5.3Entity Body
The Content-Type entity-header field indicates the media type of the entity body. The
Content-Type
may
be
designated
as
application/xml;
charset=UTF-8,
application/octet-stream, etc.
For configuration information,
charset=UTF-8. For example,
the
Content-Type
is
usually
application/xml;
HTTP Request Message:

GET /System/status HTTP/1.1
HTTP Response Message:

HTTP/1.1 200 OK
Content-Type: application/xml; charset=UTF-8
<?xml version=1.0 encoding=UTF-8?>

<DeviceStatus version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
</DeviceStatus>
For data(i.e. firmware, configuration
application/octet-stream. For example,
file,
etc.),
the
Content-Type
may
be
HTTP Request Message:

PUT /System/configurationData HTTP/1.1
Content-Type: application/octet-stream
[proprietary configuration file data content ]

HTTP Response Message:
HTTP/1.1 200 OK

<ResponseStatus version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
</ResponseStatus>
4.5.4Operations
Different resources will specify different operation.
The set device configuration resources use PUT operation. If there is an XML
block parameter for the request, the inbound XML format is defined according to
a resource-special XML schema. Request status will be returned by the XML
response information of the device, and can be used for indicating the PUT
operation status. The responded XML format is defined by XML Response
Schema (please refer to section 4.5.5 for detail description). After the device
configuration is updated successfully, it will return an XML response with status
code OK; while another status code will be used for indicating unsuccessful
operations. In either case, the device only responses after it is ready to continue
normal operation, i.e. accepting streaming request, receiving configuration
commands, etc.
The get device configuration resources use GET operation. After a successful
GET operation, the result will be returned in XML format according to the
resource description. For an unsuccessful request (i.e. users is not
authenticated), the result will be returned in XML format according to XML
Response Schema.
Resources to create device configurations information will use the POST
operation. If there is an XML block parameter for the request, the inbound XML
format is defined according to a resource-special XML schema. The request
status will be indicated by the XML response information returned from the
device, and can be used to indicate the status of the POST operation. This XML
format is defined according to XML Response Schema (see section 4.5.5 for
details). After successfully creating the data, the device returns an XML response
with status code OK. A separate status code is used for unsuccessful
operations.
Resources to delete device configurations information will use the Delete
operation. If successful, the result will be returned an XML response with status
code OK. A separate status code is used for unsuccessful operations. This XML
format is defined according to XML Response Schema (see section 4.5.5 for
details).
Data uploading resources (i.e. firmware upgrade, import configuration, etc.) will
use PUT operation. The content of the data will be stored in the body of the
HTTP request. If successful, the result will be returned an XML response with
status code OK. A separate status code is used for unsuccessful operations.
This XML format is defined according to XML Response Schema (see section
4.5.5 for details).
Data receiving resources (i.e. export configuration file) use GET operation. If
successful, the result will be returned the data according to the resource
description. An XML block is used for unsuccessful operations. This XML format
is defined according to XML Response Schema (see section 4.5.5 for details).
For Special Resources, GET operation will be used. For more detailed
description see Section 6.
If there is an XML block for the HTTP request or response, the Content-Type and
Content-Length will be set in the headers of the HTTP message.
4.5.5Error Handling
As with any other protocol, errors may occur during communications, protocol or message
processing, and the specification classifies error handling into categories below:
Protocol Errors, which are result of an incorrectly formed protocol message.

Protocol Errors may contain header value or be received in an not expected or
experience a socket timeout. To indicate and interpret protocol error, HTTP
protocol has defined a set of standard status codes [e.g., 1xx, 2xx, 3xx, 4xx, 5xx].
According to this specification, the IP devices will use appropriate HTTP protocol
defined status codes for error reporting and when received handle accordingly.
Application Errors, which are generated as a result of REST operations errors.
All such application errors must be reported and handled through HTTP
messages. The following table indicates the mapping relationship between HTTP
status codes and REST operations, and also the information contained in
response header and bodies.
Table 3
HTTP
Status
Codes
REST Meaning
GET
PUT
200
OK-The
request
has
succeeded.
Header Notes: None
Body Notes: The requested
resource will be returned in the
body.
201
Created- The request has

created a new resource.
Header Notes: The Location
header contains the URI of the
newly created resource.
Body Notes: The response
returns an entity describing the
newly created resource.
204
No Content The request

succeeded, but there is no data
to return.
Header Notes: None
Body Notes: No body is allowed.
301
Moved Permanently The

requested resource has moved
permanently.
Header contains the URI of the
new location.
Body Notes: The body may
contain the new resource
location.
POST
DELETE
HTTP
Status
Codes
REST Meaning
GET
302
Found The requested

resource should be accessed
through this location, but the
resource actually lives at another
location. This is typically used to
set up an alias.
header contains the URI of the
resource.
Body Notes: The body may
contain the new resource
location.
400
Bad Request The request

was badly formed. This is
commonly used for creating or
updating a resource, but the
data
was
incomplete
or
incorrect.
Header
Notes:
The
Reason-Phrase sent with the
HTTP status header may contain
information on the error.
Body Notes: The response may
contain more information of the
underlying error that occurred in
addition to the Reason-Phrase.
401
Unauthorized The request

requires user authentication to
access this resource. If the
request
contains
invalid
authentication data, this code is
sent.
Header Notes: At least one
authentication mechanism must
be
specified
in
the
WWW-Authenticate header. The

10
PUT
POST
DELETE
HTTP
Status
Codes
REST Meaning
GET
PUT
POST
DELETE
403
Forbidden The request is not

allowed because the server is
refusing to fill the request. A
common reason for this is that
the device does not support the
requested functionality.
Header
Notes:
The
404
Not Found The requested

resource does not exist.
Header Notes: None
Body Notes: None
405
Method Not Allowed The

request used an HTTP method
that is not supported for the
resource
because
the
specification does not allow this
method. If the device does
support the functionality but it is
a valid operation (that has been
defined in this specification),
then 403 is returned.
Header Notes: The Allow header
lists the supported HTTP
methods for this resource.
Body Notes: None
500
Internal Server Error - An

internal
server
error
has
occurred.
Header Notes: None
Body Notes: None


11
HTTP
Status
Codes
REST Meaning
GET
PUT
POST
DELETE
503
Service Unavailable The

HTTP Server is up, but the
REST service is not available.
Typically this is caused by too
many client requests.
Header Notes: The Retry-After
header suggests to the client
when to try resubmitting the
request.
Body Notes: None
Responses to many resources calls contain data in XML format. XML Response
Schema is defined in Annex. XML Response Schema consists of the following
sections:
requestURI - the URI of the corresponding HTTP request message
statusCode - indicating the status of the REST operations.

Table 4
statusCode
Description
OK - indicate a successful operation is done (remark: if the request

contains some parameters that are not supported, the device will ignore
those parameters and return OK as statusCode)
Device Busy - for a command which cannot be processed at that time

(i.e. if the device receives a reboot command during upgrading process)
Device Error - if the device can not perform the request for a hardware
error. An error message in statusString format to indicate operation
failure
Invalid Operation - either if the operation is not supported by the device,

or if the user has not passed the authentication, or if the user does not
have enough privilege for this operation
Invalid XML Format - if the XML format is not recognized by the system.
There will be statusString returned to represent different errors
Invalid XML Content - an incomplete message or a message containing

an out-of-range parameter. Relative statusString will be return.
Reboot Required - If a reboot is required before the operation taking

effect
statusString error type for the not completed operation.

id Return the ID created by the device in POST operation

12
4.6 Namespaces
The namespace xmlns:hik=http://www.hikvision.com/ver10/XMLSchema is used in this
specification.
The following namespaces are referenced by this specification:
xmlns:xs=http://www.w3.org/2001/XMLSchema
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xmlns:xlink=http://www.w3.org/1999/xlink
4.7 Security
User-based access control is adopted in this specification. Security policy configuration in
this specification based on three different user levels.
Administrator the privilege can access all supported resources on IP device.
Operator the privilege can access some general-level and higher-level

resources. See the Resource Description of each resource for details.
Viewer the privilege can only access some general-level resources. See the
Resource Description of each resource for details.
In order to access all supported resources, one account with Administrator privilege level
must be active at all times. A default user account admin is provided by all IP devices. It
has an Administrator user level, and must not be deleted. Its default password is 12345.
5 Device discovery
The IP devices support Universal Plug and Play (UPnP) technology to discovery/locate
themselves. A UPnP compatible device will automatically announce its network address,
supported devices and services types when connected to a network, and therefore
becoming plug-and-play by allowing clients recognize those information and begin using
this device immediately.
The UPnP architecture supports zero-configuration networking, and the device can
dynamically join a network, obtain IP address, announce its name, convey its capabilities
upon request, and gets the on-line status and capabilities of other devices. DHCP and
DNS servers are optional and are only used if they are available on the network. Devices
can leave the network automatically without leaving any unwanted status information
behind. UPnP was published as a 73-part International Standard, ISO/IEC 29341, in
December, 2008 [6][7][8].
13
The foundation for UPnP networking is IP addressing. When a device is connected to the
network for the first time, its Dynamic Host Configuration Protocol (DHCP) client will
search for a DHCP server. If the device successfully get its domain name via DNS server
or DNS forwarding, then it should use this domain name for the following network
operations; if the network is unmanaged and no DHCP server is found, the device must
assign an address for itself, which is known as AutoIP of the UPnP Device Architecture
[9][10], and use this IP address for the following network operations.
Once given an IP address, the Discovery process will be executed in UPnP networking.
The UPnP discovery protocol is also knows as Simple Service Discovery Protocol (SSDP).
When a device is added to the network, SSDP allow that device to announce its services
to the control points on the network. Similarly, when a control point is added to the network,
SSDP allows that control point to search for relative devices on the network. During the
above searching or announcing process, a a discovery message which contains essential
device specifics or one of its services will be transfered, for example, device type,
identifier, and a pointer to more detailed information.
After a control point has discovered a device, the control point still needs more operations
to request more information about the device or to interact with it. An HTTP GET request
for mandatory index Special Resource will return a list of the resources supported by the
device.
Remark: the index resource will only return the first level resources of a node, while the
indexr Special Resource will return a complete folder list in tree structure with the current
resource as root folder.
6 Resource Description
6.1 Resource Description Outline
Each resource in this specification is defined using the following format.
Resource_URI
Type
Operation_Name
Version
User Lever
Description
Description of the operation.
Query
Indicates the name/value pairs (p1, p2, p3,,pn) for the resource.
Inbound Data
Indicates inbound data for the resources.
Success Return
the Type (if present) and the name of XML Data Block
Notes: describes any special processing rules for the resource.

14
Type refers to Special Resource, Service and General Resource.

Version is used to determine the version of the protocol. The version number shall be set
to 1.0 in this specification.
Operation_Name refers to GET, PUT, POST and DELETE.
Inbound Data includes three types as follows:
NONE no input data
DataBlock the name of an XML Data Block. Datablocks used here must be
defined according to the specification.
Mime type mime type for the input data in the HTTP payload. Remark:
application/ xml is not a valid mime type.
If a device does not support particular XML tags or blocks, then it may not be supported by
the resource operations.
Generally, if a field is not provided in the inbound XML, then its current values shall not be
modified in the devices repository.
If a required field did not exist in the devices repository, then it must be provided in the
applicable resource operations.
Success Return and Error Return detailed description see Section 4.5.5.
6.2 Built-in Types

Table 5
Type
Description
BaudRate
A positive numerical value indicating the data transmission rate in symbols

per second.
Value is >=0.
Example: 9600
Color
RGB triplet in hexadecimal format (3 bytes) without the preceding "0x".

Example: FF00FF
Coordinate
A positive numerical value in pixels. A coordinate pair of 0,0 (x,y) indicates

the
bottom-left corner of the video image.
Value is >=0.
Maximum value is dependent on video resolution.
FPS
Frame rate multiplied by 100.

Example: 2500 [PAL]
IPv4
Address
Notation is xxx.xxx.xxx.xxx
Example: 3.137.217.220
MAC
MAC Address
Notation is aa:bb:cc:dd:ee:ff with 6 hex bytes.

15
6.3 Annotation
The XML Data Blocks described in this document contains annotations for the fields
properties. Please refer to the XML schema definitions for detail description.
The following annotation content is inserted into the comments to describe the data
carried in the field:
Table 6
Annotation
Description
req
Required field.
opt
Optional field. For data uploaded to the device, if the field is present but the
device does not support it, it should be ignored.
dep
This field is required depending on the value of another field.
ro
Read-only. For XML data that is both read and written to the device, this
field is only present in XML returned from the device. If this field is present
in XML uploaded to the device, it should be ignored.
wo
Write-only. This field is only present in XML that can be uploaded to the
device. This field should never be present in data returned from the device.
[This is used for uploading passwords].
xs:<type>
A type defined in XML Schema Part 2: Datatypes Second Edition, see

http://www.w3.org/TR/xmlschema-2
Remark: optional XML structures may contain required fields for the operation, which
mean that even if the entire XML block is optional, some of its contained fields may still be
necessary if required.
7 Special Resources
7.1 index
index
Special Resource
GET
v1.0
Viewer
Description
Enumerate child resources of a resource.
Query
None
Inbound Data
None
Success Return
hik:ResourceList ResourceList
Notes: Returns a non-recursive resource listing of all child resources.

16
7.2 indexr
indexr
Special Resource
GET
v1.0
Viewer
Description
Enumerate child resources of a resource.
Query
None
Inbound Data
None
Success Return
hik:ResourceList ResourceList
Notes: Returns a recursive resource listing of all child resources.
7.3 description
description
Special Resource
GET
v1.0
Viewer
Description
Describe the corresponding resource
Query
None
Inbound Data
None
Success Return
hik:ResourceDescription ResourceDescription
Notes: <version> set the version of resource. In this specification, its value is 1.0.
A version attribute is included in the description. This means resources with different
versions may exist within the same Services. In that case, the version of Services is the
version of the contained resource with the lowest version, and all resources in the
Services container must be backward compatible. If any resource of a Service container
can not maintain backward compatibility with previous versions, a new Services version
should be introduced.
7.4 capabilities
capabilities
Special Resource
GET
v1.0
Viewer
Description
Describe the capabilities of the corresponding resource
Query
None
Inbound Data
None
Success Return
the XML Data Block resource-specified
Notes:
For the General Resource, which inbound data is specified as an XML payload, the
17
Special Resource (capabilities) is provided for video management systems or client

applications to query an IP device and understand what XML tags are supported.
Capabilities is essentially an XML instance of the corresponding General Resource XML
Data Block. Capabilities must contain the acceptable values for each attribute.
While XML Schema Document are also required of any XML data defined by this
specification and xsd documents are capable of defining the acceptable range of values
for any attribute, using a global xsd to define capacities would imply that all devices
support the same options for any parameter. By allowing devices to respond to the
capabilities request, each device can support different values for any attribute, within the
constraints of the schema.
Table 7
Capabilities
Attribute
min
max
range
Description
Syntax
Applicable
XML Data
Types
The minimum character

length for a string, or the
minimum numerical value of
a number
Examples:
min=0
min=19
min=-74(numerical
only)
min=1.6
All except fixed

data types1)
The maximum character

length for a string, or the
maximum numerical value
of a number
Examples:
max=4
max=37
max=8192
max=14.61
All except fixed

data types1)
Indicates the possible range

of numerical values within
the
min
and
max
attributes of an element.
This attribute should only be
used if the possible value
for an XML element does
not include the entire
numerical range between
min and max attributes
Ranges are listed in

numerical
order
separated by a ,
character. A range has
the form x~y where x is
the range floor and y is
the range ceiling. Single
numbers may also be
used.
All
numerical
data types
Example: if an XML
element supports values
0, 456, 1674 to 2009
and 2012, the syntax
would be: range=0,
456, 1674~2009, 2012
18
Capabilities
Attribute
opt
Description
Syntax
Lists the supported options

for a CodeID data type.
Required for XML elements
with a CodeID data type.
This attribute should not be
used for any other data type
If
all
options
are
supported, the syntax is
all.
Otherwise,
supported options are
listed separated by a ,
character.
Applicable
XML Data
Types
CodeID
Examples:
opt=all
opt=1, 4, 6, 7
Examples:
def=7416
def=ace
All data types
def
Indicates the default value

of the XML element. If the
element has not default
value, this attribute should
not be used
reqReboot=true
All data types
reqReboot
Indicates if configuration of
this XML element requires a
device reboot before taking
effect. If an element does
not require a boot, this
attribute should not be used
dynamic
Size
Indicates if an XML element dynamic=true

has dynamic capabilities
dependent on other XML
configuration. For example,
if an elements data range
changes based on another
elements configured value,
this attribute must be used.
In this case, the elements
capability attributes must
always reflect the current
device configuration
All data types
Indicates the maximum

number of entries in an XML
List. This attribute is only
applicable to XML list
elements. This attribute
should not be used for any
other type of element
Only supported
for list elements

19
Example: If a device
supports 16 users the
example would be
<UserList size=16>
<User>
</UserList>
1) Fixed, pre-defined data types do not need certain capability attributes because their
formats/data ranges are already defined.
Special Resources do not contain themselves.
The requestURIs /index, /indexr, /description are required.
8 Services and General Resources

8.1 System
/System
Service v1.0
Notes:
8.1.1Device Information
/System/deviceInfo
General Resource v1.0
GET
Viewer
Description
It is used to get device information.
Query
None
Inbound Data
None
Success Return
DeviceInfo
PUT
Administrator
Description
It is used to update device information.
Query
None
Inbound Data
DeviceInfo
Success Return
hik:ResponseStaus ResponseStatus
Notes:
Some fields are read-only and may not be set. If these fields are present in the inbound
XML block, they are ignored.
For the <DeviceInfo> uploaded to the device during a PUT operation, all fields are
considered optional and any fields that are not present in the inbound XML are not
changed on the device. This allows setting of the fields individually without having to load
the entire XML block to the device.
<deviceDescription> is a description of the device as defined in RFC1213.
For IPC the <deviceDescription> value is IPCamera;
For IP speed Dome the <deviceDescription> value is IPDome;
For DVR or DVS the <deviceDescription> value is DVRDVS;
20
<deviceLocation> is the location of the device as defined in RFC1213

<systemContact> is the contact information for the device as defined in RFC1213.
DeviceInfo XML Block
<DeviceInfo version="1.0" xmlns="http://www.hikvision.com/ver10/XMLSchema">
<deviceName>

</deviceName>
<deviceID>

</deviceID>

<deviceDescription> 
</deviceDescription>
<deviceLocation>

</deviceLocation>
<systemContact>
</systemContact>
<model>
</model>
<serialNumber>
</serialNumber>
<macAddress>
 </macAddress>
<firmwareVersion>
</firmwareVersion>
<firmwareReleasedDate> 
</firmwareReleasedDate>
<bootVersion>

</bootVersion>
<bootReleasedDate>
</bootReleasedDate>
<hardwareVersion>
</hardwareVersion>
</ DeviceInfo>
8.1.2Configuration file(s)
/System/configurationFile
GET
Administrator
Description
It is used to get devices configuration file(s).
Query
None
Inbound Data
None
Success Return
Opaque Data
PUT
Administrator
Description
It is used to update devices configuration file(s).
Query
None
Inbound Data
Opaque Data
Success Return
Notes:
Configuration file is device-dependant it may be binary or any other format.

Should reboot device after configuration file is applied.

21
8.1.3Factory default
/System/factoryDefault
PUT
Administrator
Description
It is used to reset the configuration for the device to the factory

default.
Query
mode
Inbound Data
None
Success Return
Notes:
Two factory reset modes are supported:

full resets all device parameters and settings to their factory values.
basic resets all device parameters and settings except the values in Network Service.
The default mode is full.
The device should be rebooted after it is reset.
8.1.4Firmware upgrade
/System/firmwareUpgrade
PUT
Administrator
Description
It is used to upgrade the firmware of the device.
Query
None
Inbound Data
Opaque Data
Success Return
Notes:
The device should be rebooted after the upgrade is completed.
8.1.5Reboot
/System/reboot
PUT
Administrator
Description
It is used to reboot the device.
Query
None
Inbound Data
None
Success Return
Notes:
ResponseStatus is returned before the device proceeds to reboot.

22
8.1.6Status
/System/status
GET
Viewer
Description
It is used to get the status information of the device.
Query
None
Inbound Data
None
Success Return
DeviceStatus
Notes:
DeviceStatus XML Block

<DeviceStatus version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<currentDeviceTime> 
</currentDeviceTime>
<deviceUpTime>
 </deviceUpTime>
<CPUList>

<CPU>
<cpuDescription> 
</cpuDescription>
<cpuUtilization>  </cpuUtilization>
</CPU>
</CPUList>
<MemoryList>

<Memory>
<memoryDescription> 
</memoryDescription>
<memoryUsage>
 </memoryUsage>
<memoryAvailable>
 </memoryAvailable>
</Memory>
</MemoryList>
</DeviceStatus>
8.1.7Time
/System/time
GET
Viewer
Description
It is used to get the device time information.
Query
None
Inbound Data
None
Success Return
Time
PUT

23
Administrator
Description
It is used to udpate the device time information.
Query
None
Inbound Data
Time
Success Return
Notes:
If <timeMode> is present and set to local, the <localTime> and <timeZone> fields are
required. The <localTime> block sets the device time.
If <timeMode> is present and set to NTP, only the <timeZone> field is required. The
device time is set by synchronizing with NTP.
Time XML Block
<Time version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<timeMode> 
</timeMode>
<localTime>

</localTime>
<timeZone> 
</timeZone>
</Time>
8.1.8LocalTime
/System/time/localTime
GET
Viewer
Description
It is used to get the device local time information.
Query
None
Inbound Data
None
Success Return
ISO 8601 Date-Time String
PUT
Administrator
Description
It is used to udpate the device local time information.
Query
None
Inbound Data
ISO 8601 Date-Time String
Success Return
Notes:
An ISO 8601 Date/Time string is accepted and returned. If the date/time value has a time
zone, the time is converted into the devices local time zone.
If the device time mode is set to ntp setting this value has no effect.
8.1.9TimeZone
/System/time/timeZone
24
GET
Viewer
Description
It is used to get the device time zone information.
Query
None
Inbound Data
None
Success Return
Time zone string
PUT
Administrator
Description
It is used to udpate the device time zone information.
Query
None
Inbound Data
Time zone string
Success Return
Notes:
Time zones are defined by POSIX 1003.1 section 8.3 time zone notations. Note that the
value following the +/- is the amount of time that must be added to the local time to result
in UTC.
Example:
EST+5EDT01:00:00,M3.2.0/02:00:00,M11.1.0/02:00:00
Defines eastern standard time as EST with a GMT-5 offset. Daylight savings time is
called EDT, is one hour later and begins on the second Sunday of March at 2am and
ends on the first Sunday of November at 2am.
CET-1CEST01:00:00,M3.5.0/02:00:00,M10.5.0/03:00:00
Defines central European time as GMT+1 with a one-hour daylight savings time
(CEST) that starts on the last Sunday in March at 2am and ends on the last Sunday in
October at 3am.
8.1.10
NtpServers
/System/time/ntpServers
GET

Viewer
Description
It is used to get the configuration of NTP servers for the device.
Query
None
Inbound Data
None
Success Return
NTPServerList
PUT
Administrator
Description
It is used to update the configuration of NTP servers for the device.
Query
None

25
Inbound Data
NTPServerList
Success Return
POST
Administrator
Description
It is used to add the configuration of a NTP server for the device.
Query
None
Inbound Data
NTPServer
Success Return
DELETE
Administrator
Description
It is used to delete the configuration of NTP servers for the device.
Query
None
Inbound Data
None
Success Return
Notes:
When the <timeMode> is set to NTP, the servers in this list are used to synchronize the
devices system time.
NTPServerList XML Block
<NTPServerList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<NTPServer/> 
</ NTPServerList>
8.1.11
NtpServer
/System/time/ntpServers/ID
GET

Viewer
Description
It is used to get the configuration of a NTP server for the device.
Query
None
Inbound Data
None
Success Return
NTPServer
PUT
Administrator
Description
It is used to update the configuration of a NTP server for the device.
Query
None
Inbound Data
NTPServer
Success Return
DELETE
Administrator
Description
It is used to delete the configuration of a NTP server for the device.
Query
None
Inbound Data
None
Success Return
Notes:

26
Depending on the value of <addressingFormatType>, either the <hostName> or the IP

address fields will be used to locate the NTP server.
NTPServer XML Block
<NTPServer version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id> 
</id>
<addressingFormatType>

</addressingFormatType>
<hostName>

</hostName>
<ipAddress>
</ipAddress>
<portNo>

</portNo>
</NTPServer>
8.1.12
Log
/System/logging
GET
Viewer
Description
It is used to get the log information of the device.
Query
majorType
minorType
startTime
stopTime
Inbound Data
None
Success Return
LogList
Notes:
The value of majorType is:

0x1:Alarm
0x2:Exception
0x3:Operation
When the value of majorType is 0x1, the value of minorType is:
0x1: alarm input
0x2: alarm output
0x3: motion detection alarm start
0x4: motion detection alarm stop
0x5: shelter alarm start
0x6: shelter alarm stop
0x21: video loss
0x22: illegal access
0x23: hard disk full

27
0x24: hard disk error

0x25: modem off-line
0x26: ip address conflict
0x27: network not connected
0x41: boot
0x42: shutdown
0x43: illegal shut down
0x50: login(local)
0x51: logout(local)
0x52: config parameter(local)
0x53: playback by file name(local)
0x54: playback by time(local)
0x55: start record(local)
0x56: stop record(local)
0x57: PTZ control(local)
0x58: preview(local)
0x59: modify date/time(local)
0x5a: upgrade software(local)
0x70: login(remote)
0x71: logout(remote)
0x72: start record(remote)
0x73: stop record(remote)
0x74: start transparent channel(remote)
0x75: stop transparent channel(remote)
0x76: get parameter(remote)
0x77: config parameter(remote)
0x78: get status(remote)
0x79: on guard(remote)
0x7a: disarm(remote)
0x7b: reboot(remote)
0x7c: start voice talk
0x7d: stop voice talk
0x7e: upgrade software(remote)
0x7f: playback by file name(remote)
0x80: playback by time(remote)
0x81: PTZ control(remote)
The format of startTime and stopTime is YYYY-MM-DDThh:mm:ss.
Devices support up to 2000 log.
LogList XML Block
<LogList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
28
<Log> 

<id>
 </id>
<time> <!req, xs:datetime --> </time>
<majorType> <!req, xs:string --> </majorType>
<minorType> <!req, xs:string -->
</minorType>
<netUser> <!req, xs:string --> </netUser>
<hostIPAddress> <!req, xs:string --> </hostIPAddress>
<channel> <!req, xs:integer --> </channel>
</Log>
</LogList>
8.1.13
Storage
/System/Storage
resource
v1.0
Notes: service of Storage
8.1.13.1 Storage/volumes
/System/Storage/volumes
GET
Viewer
Description
It is used to get the storage volumes and files information on a device
Query
None
Inbound Data
None
Success Return
StorageVolumeList
PUT
Operator
Description
It is used to update the storage volumes and files configuration on a

device.
Query
None
Inbound Data
StorageVolumeList
Success Return
Notes:
StorageVolumeList XML Block

<StorageVolumeList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<StorageVolume/> 
</StorageVolumeList>

29
8.1.13.2 Storage/volumes/ID
/System/Storage/volumes/ID
GET
Viewer
Description
It is used to get a special storage volume information on a device
Query
None
Inbound Data
None
Success Return
StorageVolume
Notes:
StorageVolume XML Block

<StorageVolume version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>
 </id>
<volumeName>  </volumeName>
<volumePath> 
</volumePath>
<volumeDescription> 
</volumeDescription>
<volumeType>

</volumeType>
<storageDescription>

</storageDescription>
<storageLocation>

</storageLocation>
<storageType>

</storageType>
<capacity>
 </capacity>
<status>  </status>
</StorageVolume>
8.1.13.3 Storage/volumes/ID/status
/System/Storage/volumes/ID/status
GET
Viewer
Description
It is used to get a special storage volume status on a device
Query
None
Inbound Data
None

30
Success Return
StorageVolumeStatus
Notes: Query the volume status. Currently only the amount of free space is returned. Devices
may extend the XML to allow for querying additional information.
StorageVolumeStatus XML Block

<StorageVolumeStatus
xmlns=http://www.hikvision.com/ver10/XMLSchema>
<freeSpace>  </freeSpace>
</StorageVolumeStatus>
version=1.0
8.1.13.4 Storage/volumes/ID/format
/System/Storage/volumes/ID/format
PUT
Viewer
Description
It is used to format a storage device
Query
None
Inbound Data
None
Success Return
StorageVolumeStatus
Notes:Formating may take time.
8.1.13.5 Storage/volumes/ID/isFormat
/System/Storage/volumes/ID/IsFormat
GET
Viewer
Description
It is used to access the procedure of formating
Query
None
Inbound Data
None
Success Return
StorageVolumeFormatSatus
Notes: formatSatus show the percentage of formatted part of the storage device.
StorageVolumeStatus XML Block

<StorageVolumeFormatSatus
<formatSatus></formatSatus>
</StorageVolumeFormatSatus>

31
version=1.0
8.1.14
FishEye
/System/fisheye
GET
Viewer
Description
It is used to get the fisheye configuration on a device.
Query
None
Inbound Data
None
Success Return
FishEye
PUT
Administrator
Description
It is used to update the fisheye configuration on a device.
Query
None
Inbound Data
FishEye
Success Return
Notes:
FishEye XML Block

<FishEye version=1.0 xmlns= http://www.hikvision.com/ver10/XMLSchema>
<type>  </Type>
<realTimeOutput>  < realTimeOutput >
</FishEye>
8.2 Network
/Network
Service v1.0
Notes: Network configuration.
8.2.1Interfaces
/Network/interfaces
GET
Viewer
Description
It is used to get the device network interfaces.
Query
None
Inbound Data
None
Success Return
NetworkInterfaceList
Notes:
As hardwired system resources, network interfaces cannot be created or destroyed.

32
NetworkInterfaceList XML Block

<NetworkInterfaceList version=1.0
<NetworkInterface/> 
</NetworkInterfaceList>
8.2.2Interface
/Network/interfaces/ID
GET
Viewer
Description
It is used to get a particular network interface.
Query
None
Inbound Data
None
Success Return
NetworkInterface
PUT
Administrator
Description
It is used to update a particular network interface.
Query
None
Inbound Data
NetworkInterface
Success Return
Notes:
NetworkInterface XML Block

<NetworkInterface version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>

</id>
<IPAddress/> 
<Discovery/> 
<PPPoE /> 
<DDNS /> 
</NetworkInterface>
8.2.3IPAddress
/Network/interfaces/ID/ipAddress
GET

Viewer
Description
It is used to get the ip address of a particular network interface.
Query
None
Inbound Data
None
Success Return
IPAddress
PUT
Description
Administrator
It is used to update the ip address of a particular network interface.

33
Query
None
Inbound Data
IPAddress
Success Return
Notes:
If <addressingType> is dynamic, fields below it need not be provided.

If <addressingType> is dynamic, a DHCP client is used for the device.
If <addressingType> is static the device IP address is configured manually and the
gateway and DNS fields are optional.
<subnetMask> notation is xxx.xxx.xxx.xxx.
IPAddress XML Block
<IPAddress version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<ipVersion>
 </ipVersion>
<addressingType>  </addressingType>
<ipAddress>
</ipAddress>
<subnetMask>

</subnetMask>
<DefaultGateway> 
<ipAddress>
</ipAddress>
</DefaultGateway>
<PrimaryDNS>

<ipAddress>
</ipAddress>
</PrimaryDNS>
</IPAddress>
8.2.4Wireless
/Network/interfaces/ID/wireless
GET
Viewer
Description
It is used to get the WIFI information of a wireless network interface.
Query
None
Inbound Data
None
Success Return
Wireless
PUT
Administrator
Description
It is used to update the WIFI information of a wireless network

interface.
Query
None
Inbound Data
Wireless
Success Return
Notes:
If the <securityMode> field is "WEP, the <WEP> block must be provided.

34
If the <securityMode> field is "WPA or WPA2-personal", the <WPA> block must be

provided.
<channel> corresponds to an 802.11g wireless channel number or auto for
autoconfiguration.
<wmmEnabled> enables 802.11e, QoS for IEEE 802.11 networks (Wi-Fi Multimedia)
<defaultTransmitKeyIndex> indicates which encryption key is used for WEP security.
<encryptionKey> is the WEP encryption key in hexadecimal format.
<sharedKey> is the pre-shared key used in WPA
Wireless XML Block
<Wireless version=1.0 xmlns="http://www.hikvision.com/ver10/XMLSchema">
<enabled>  </enabled>
<wirelessNetworkMode>

</wirelessNetworkMode>
<channel>  </channel>
<ssid>  </ssid>
<wmmEnabled>  </wmmEnabled>
<WirelessSecurity> 
<securityMode>

</securityMode>
<WEP> 
<authenticationType>

</authenticationType>
<defaultTransmitKeyIndex>  </defaultTransmitKeyIndex>
<wepKeyLength>  </wepKeyLength>
<wepKeyType> </wepKeyType>
<EncryptionKeyList>
<encryptionKey>

</encryptionKey>
</EncryptionKeyList>
</WEP>
<WPA> 
<algorithmType>  </algorithmType>
<sharedKey>  </sharedKey>
<wpaKeyLength></wpaKeyLength>
</WPA>
</WirelessSecurity>
</Wireless>
35
8.2.5DetectedWirelessList
/Network/interfaces/ID/detectedWirelessList
GET
Viewer
Description
It is used to get all detected wireless networks.
Query
None
Inbound Data
None
Success Return
detectedWirelessList
detectedWireless XML Block

<DetectedWirelessList version=1.0
xmlns="http://www.hikvision.com/ver10/XMLSchema">
<DetectedWireless/>
</DetectedWirelessList>
8.2.6DetectedWireless
/Network/interfaces/ID/detectedWirelessList/ID
GET
Viewer
Description
It is used to get a special detected wireless network.
Query
None
Inbound Data
None
Success Return
detectedWireless
detectedWirelessList XML Block

<DetectedWireless version=1.0 xmlns="http://www.hikvision.com/ver10/XMLSchema">
<id> 
</id>
<wirelessNetworkMode>

</wirelessNetworkMode>
<channel>  </channel>
<ssid>  </ssid>
<speed> </speed>
<signalStrength>
</securityMode>
</DetectedWireless>
8.2.7Discovery
/Network/interfaces/ID/discovery
GET
Viewer
Description
It is used to get the discovery settings of a particular network

interface.
Query
None
Inbound Data
None
Success Return
Discovery
PUT
Administrator
Description
It is used to update the discovery settings of a particular network

interface.
Query
None
Inbound Data
Discovery
Success Return
Notes:
Discovery XML Block

<Discovery version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<UPnP>

<enabled>
 </enabled>
</UPnP>
<Zeroconf>

<enabled>
</Zeroconf>
</Discovery>
8.2.8PPPoE
/Network/interfaces/ID/pppoe
GET

Viewer
Description
It is used to get the PPPoE configuration of a particular network

interface.
Query
None

37
Inbound Data
None
Success Return
PPPoE
PUT
Administrator
Description
It is used to update the PPPoE configuration of a particular network

interface.
Query
None
Inbound Data
PPPoE
Success Return
Notes:
<password> is a write-only field.

PPPoE XML Block
<PPPoE version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled>
<userName>
 </userName>
<password>
 </password>
<dynamicIP>
 </ dynamicIP >
</PPPoE>
8.2.9DDNS
/Network/interfaces/ID/ddns
GET

Viewer
Description
It is used to get DDNS configuration of a particular network interface.
Query
None
Inbound Data
None
Success Return
DDNS
PUT
Administrator
Description
It is used to update DDNS configuration of a particular network

interface.
Query
None
Inbound Data
DDNS
Success Return
Notes:
When <provider> is IPServer, <serverIPAddress> is required.

When <provider> is DysDNS, all fields are required except the <portNo>.
When <provider> is PeanutHall, all fields are required except the <serverIPAddress>
and <portNo>.
DDNS XML Block
38
<DDNS version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>

<provider>  </provider>
<serverIPAddress> <!dep, xs:string --> </serverIPAddress>
<portNo>  </portNo>
<domainName>  </domainName>
<userName>  </userName>
<password> </password>
</DDNS>
8.2.10
NFSList
/Network/interfaces/ID/NFSList
GET
Viewer
Description
It is used to get the configuration of NFSs for a particular network

interface.
Query
None
Inbound Data
None
Success Return
NFSList
PUT
Administrator
Description
It is used to update the configuration of NFSs for a particular network

interface.
Query
None
Inbound Data
NFSList
Success Return
Notes:
NFSList XML Block

<NFSList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<NFS/>
</ NFSList >
8.2.11
NFS
/Network/interfaces/ID/NFSList/ID
GET

Viewer
Description
It is used to get the NFS configuration of a particular network

interface.
Query
None

39
Inbound Data
None
Success Return
NFS
PUT
Administrator
Description
It is used to update the NFS configuration of a particular network

interface.
Query
None
Inbound Data
NFS
Success Return
Notes:
NFS XML Block

<NFS version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>  <id>
<NFSIPAddress>
 </ NFSIPAddress >
<NFSDirectory>
 </ NFSDirectory >
</ NFS >
8.2.12
Adapter
/Network/interfaces/ID/Adapter
GET
Viewer
Description
It is used to get the adapter configuration of a particular network

interface.
Query
None
Inbound Data
None
Success Return
Adapter
PUT
Administrator
Description
It is used to update the adapter configuration of a particular network

interface.
Query
None
Inbound Data
Adapter
Success Return
Notes:
<mode> identifies the transmission speed mode of network interface card

The following speed mode are supported:
10M/half-duplex
10M/duplex
100M/half-duplex
100M/duplex
auto
40
NFS XML Block

<Adapter version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<description>
 </description>
<mode>
 </mode>
</Adapter>
8.2.13
Examples
Example: Getting the Network Settings

GET /Network/interfaces HTTP/1.1
HTTP/1.1 200 OK
Content-Length: xxx
<NetworkInterfaceList version=1.0
<NetworkInterface>
<id>1</id>
<IPAddress>
<ipVersion>v4</ipVersion>
<addressingType>static</addressingType>
<ipAddress>172.6.64.7</ipAddress>
<subnetMask>255.255.255.0</subnetMask>
<DefaultGateway>
</DefaultGateway>
<PrimaryDNS>
</PrimaryDNS>
</IPAddress>
<Discovery>
<UPnP>
<enabled>true</enabled>
</UPnP>
<Zeroconf>
</Zeroconf>
41
</Discovery>
<PPPoE>
<userName>hikvision</userName>
</PPPoE>
<DDNS>
<provider>PeanutHall</provider>
<domainName>hikvision.vicp.net</domainName>
<userName>hikvision</userName>
</DDNS>
<NetworkInterface>
</NetworkInterfaceList>
Example: Setting the IP Address
PUT /Network/interfaces/1/ipAddress HTTP/1.1

Content-Length: xxx
<IPAddress version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<ipVersion>v4</ipVersion>
<addressingType>static</addressingType>
<subnetMask>255.255.255.0</subnetMask>
<DefaultGateway>
</DefaultGateway>
<PrimaryDNS>
</PrimaryDNS>
</IPAddress>
HTTP/1.1 200 OK

Content-Length:xxx
<ResponseStatus version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<requestURL>/Network/interfaces/1/ipAddress</requestURL>
42
<statusCode>1</statusCode>
<statusString>OK</statusString>
</ResponseStatus>
8.3 IO
/IO
Service v1.0
GET
Viewer
Description
It is used to get the I/O ports information.
Query
None
Inbound Data
None
Success Return
IOPortList
Notes:
The allocation of IDs between input and output ports must be unique.
IOPortList XML Block
<IOPortList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<IOInputPortList/>

<IOOutputPortList/> 
</IOPortList>
8.3.1Status
/IO/status
GET
Viewer
Description
It is used to get the status of the I/O ports.
Query
None
Inbound Data
None
Success Return
IOPortStatusList
Notes:
<ioPortID> refers to /IO/inputs/ID or /IO/outputs/ID. The port IDs are guaranteed to be

unique across input and output ports.
<ioState> indicates whether the input port is active or inactive. In most applications, a high
signal is considered active.
IOPortStatus XML Block
<IOPortStatusList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<IOPortStatus> 

43
<ioPortID> 

<ioPortType> 
<ioState>

</IOPortStatus>
</IOPortStatusList>
</ioPortID>
</ioPortType>
</ioState>
8.3.2Inputs
/IO/inputs
GET
Viewer
Description
It is used to get the Input ports information.
Query
None
Inbound Data
None
Success Return
IOInputPortList
Notes:
IO inputs are hardwired, meaning that the inputs are statically allocated by the device and
cannot be created or deleted.
IOInputPortList XML Block
<IOInputPortList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<IOInputPort/> 
</IOInputPort>
8.3.3Input
/IO/inputs/ID
GET
Viewer
Description
It is used to get particular input port information.
Query
None
Inbound Data
None
Success Return
IOInputPort
PUT
Operator
Description
It is used to update particular input port information.
Query
None
Inbound Data
IOInputPort
Success Return
Notes:
<triggering> indicates the signal conditions to trigger the input port. High/Low will
44
continuously trigger for the duration of high/low input signal.

IOInputPort XML Block
<IOInputPort version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>

</id>
<triggering>  <triggering>
</IOInputPort>
8.3.4Input status
/IO/inputs/ID/status
GET
Viewer
Description
It is used to get the status of a particular input port.
Query
None
Inbound Data
None
Success Return
IOPortStatus
Notes:
See /IO/status for an explanation of the fields.
8.3.5Outputs
/IO/outputs
GET
Viewer
Description
It is used to get the output ports information.
Query
None
Inbound Data
None
Success Return
IOOutputPortList
Notes:
IO outputs are hardwired, meaning that the outputs are statically allocated by the device
and cannot be created or deleted.
IOOutputPortList XML Block
<IOOutputPortList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<IOOutputPort/> 
</IOOutputPort>

45
8.3.6Output
/IO/outputs/ID
GET
Viewer
Description
It is used to get particular output port information.
Query
None
Inbound Data
None
Success Return
IOOutputPort
PUT
Operator
Description
It is used to update particular output port information.
Query
None
Inbound Data
IOOutputPort
Success Return
Notes:
<PowerOnState> defines the output port configuration when the device is powered on.
<defaultState> is the default output port signal when it is not being triggered.
<outputState> is the output port signal when it is being triggered. Pulse will cause the
output port to send a signal (opposite of the <defaultState>) for a duration specified by the
<pulseDuration> tag.
<pulseDuration> is the duration of a output port signal when it is being triggered. It must
be provided if the <outputState> is pulse.
IOOutputPort XML Block
<IOOutputPort version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>
</id>
<PowerOnState>

<defaultState> <!ro, req, xs:string, high,low --> </defaultState>
<outputState>
<!ro, req, xs:string, high,low,pulse --> </outputState>
<pulseDuration>  </pulseDuration>
</PowerOnState>
</IOOutputPort>
8.3.7Output status
/IO/outputs/ID/status
GET
Viewer
Description
It is used to get the status of a particular output port.
Query
None
Inbound Data
None

46
Success Return
IOPortStatus
Notes:
See /IO/status for an explanation of the fields.
8.3.8Output trigger
/IO/outputs/ID/trigger
PUT
Operator
Description
It is used to manually trigger a particular output port.
Query
None
Inbound Data
IOPortData
Success Return
Notes:
Note that the ID used here MUST correspond to the ID in /IO/outputs/ID.

The IO output port is toggled to a high or low signal accordingly.
IOPortData XML Block
<IOPortData xmlns=http://www.hikvision.com/ver10/XMLSchema>
<outputState>
 </outputState>
</IOPortData>
8.4 Video
/Video
Service v1.0
Notes:
8.4.1Input
/Video/inputs
GET
Viewer
Description
It is used to get the video inputs configuration on an IP media device.
Query
None
Inbound Data
None
Success Return
VideoInput
Notes:
An IP media device may contain a set of video inputs. These inputs are hardwired by the
device, meaning that the IDs can be discovered but not created or deleted.

47
VideoInput XML Block

<VideoInput version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<VideoInputChannelList/> 
</VideoInput>
8.4.2Input channels
/Video/inputs/channels
GET

Viewer
Description
It is used to get the video input channels configuration on an IP

media device.
Query
None
Inbound Data
None
Success Return
VideoInputChannelList
Notes:
Since video input channels are resources that are defined by the hardware configuration
of the device, they cannot be created or deleted.
VideoInputChannelList XML Block
<VideoInputChannelList version=1.0
<VideoInputChannel/>

</VideoInputChannelList>
8.4.3Input channel
/Video/inputs/channels/ID
GET

Viewer
Description
It is used to get a particular video input channel configuration on an

IP media device.
Query
None
Inbound Data
None
Success Return
VideoInputChannel
PUT
Operator
Description
It is used to update a particular video input channel configuration on

an IP media device.
Query
None

48
Inbound Data
VideoInputChannel
Success Return
Notes:
<powerLineFrequencyMode> is used to adjust/correct video image based on different

power frequencies.
<whiteBalanceMode> indicates the white balance operational mode.
<gainLevel> indicates the gain level percentage value. 0 is low gain, 100 is high gain.
VideoInputChannel XML Block
<VideoInputChannel version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>
</id>
<powerLineFrequencyMode> 
</powerLineFrequencyMode>
<whiteBalanceMode>

</whiteBalanceMode>
<gainLevel>

</gainLevel>
<brightnessLevel>

</brightnessLevel>
<contrastLevel>

</contrastLevel>
<saturationLevel>

</saturationLevel>
<DayNightFilter>

<dayNightFilterType>

</dayNightFilterType>
</DayNightFilter>
<VideoInputChannel>
8.4.4Input channel overlay texts

/Video/inputs/channels/ID/overlays/text
GET

Viewer
Description
It is used to get the text overlays configuration for a video input

channel.
Query
None
Inbound Data
None
Success Return
TextOverlayList
PUT
Operator
Description
It is used to update the text overlays configuration for a video input

channel.
Query
None
Inbound Data
TextOverlayList

49
Success Return
POST
Operator
Description
It is used to add a text overlay for a video input channel.
Query
None
Inbound Data
TextOverlay
Success Return
DELETE
Operator
Description
It is used to delete the text overlays configuration for a video input

channel.
Query
None
Inbound Data
None
Success Return
Notes:
A set of text overlays is managed. They are composited over the video signal in increasing
ID-order.
TextOverlayList XML Block
<TextOverlayList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<TextOverlay/> 
</TextOverlayList>
8.4.5Input channel overlay text

/Video/inputs/channels/ID/overlays/text/ID
GET

Viewer
Description
It is used to get a particular text overlay configuration for a video input

channel.
Query
None
Inbound Data
None
Success Return
TextOverlay
PUT
Operator
Description
It is used to update a particular text overlay configuration for a video

input channel.
Query
None
Inbound Data
TextOverlay
Success Return
DELETE
Description
Operator
It is used to delete a particular text overlay configuration for a video
input channel.

50
Query
None
Inbound Data
None
Success Return
Notes:
<posY> value is a multiple of 16.

TextOverlay XML Block
<TextOverlay version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>

</id>
<enabled>

</enabled>
<posX>
</posX>
<posY>
</posY>
<message>
</message>
</TextOverlay>
8.4.6Input channel channelNameOverlay

/Video/inputs/channels/ID/overlays/
channelNameOverlay
GET

Viewer
Description
It is used to get a particular channel name configuration for a video

input channel.
Query
None
Inbound Data
None
Success Return
channelNameOverlay
PUT
Operator
Description
It is used to update a particular channel name configuration for a

video input channel.
Query
None
Inbound Data
channelNameOverlay
Success Return
DELETE
Operator
Description
It is used to delete a particular text overlay configuration for a video

input channel.
Query
None
Inbound Data
None
Success Return
Notes:

51
channelNameOverlay XML Block

<channelNameOverlay
<positionX>  </positionX>
<positionY>  </positionY>
<name>  </name>
</channelNameOverlay>
version=1.0
8.4.7Input channel privacyMask

/Video/inputs/channels/ID/privacyMask
GET
Viewer
Description
It is used to get the privacy masking configuration for a video input

channel.
Query
None
Inbound Data
None
Success Return
PrivacyMask
PUT
Operator
Description
It is used to update the privacy masking configuration for a video

input channel.
Query
None
Inbound Data
PrivacyMask
Success Return
Notes:
Privacy masking can be enabled and the region list configured per channel.
PrivacyMask XML Block
<PrivacyMask version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled>
</enabled>
<PrivacyMaskRegionList/> 
</PrivacyMask>
8.4.8Input channel privacyMask regions

/Video/inputs/channels/ID/privacyMask/regions
GET
Description

Viewer
It is used to get the privacy mask regions configuration for a video

52
input channel.
Query
None
Inbound Data
None
Success Return
PrivacyMaskRegionList
PUT
Operator
Description
It is used to update the privacy mask regions configuration for a video

input channel.
Query
None
Inbound Data
PrivacyMaskRegionList
Success Return
POST
Operator
Description
It is used to add a privacy mask region for a video input channel.
Query
None
Inbound Data
PrivacyMaskRegion
Success Return
DELETE
Operator
Description
It is used to delete the privacy mask regions configuration for a video

input channel.
Query
None
Inbound Data
None
Success Return
Notes:
Privacy masking consists of a set of regions that are combined to grey or black out areas
of a video input.
PrivacyMaskRegionList XML Block
<PrivacyMaskRegionList version=1.0
<PrivacyMaskRegion/> 
</PrivacyMaskRegionList>
8.4.9Input channel privacyMask region

/Video/inputs/channels/ID/privacyMask/regions/ID
GET

Viewer
Description
It is used to get a particular privacy mask region configuration for a

Query
None
Inbound Data
None
Success Return
PrivacyMaskRegion

53
PUT
Operator
Description
It is used to update a particular privacy mask region configuration for

a video input channel.
Query
None
Inbound Data
PrivacyMaskRegion
Success Return
DELETE
Operator
Description
It is used to delete a particular privacy mask region configuration for a

Query
None
Inbound Data
None
Success Return
Notes:
Region coordinates are dependent on normalized screen size.

For IPC and DVR, the normalized screen size is 4CIF704*576 under 50Hz or 704*480
under 60Hz
For IP dome, the normalized screen size is 255*255.
The computer screen coordinate system is used, which the origin coordinate is on top-left
corner , the Y axis is vertical downwards , the X axis horizontal rightwards.
Only support the rectangular region which will be drawn from four coordinates. The four
points is counterclockwise direction, and the beginning point is the top-left point.
Ordering of <PrivacyMaskRegion> blocks is insignificant.
PrivacyMaskRegion XML Block
<PrivacyMaskRegion version=1.0
<id>  </id>
<RegionCoordinatesList> 
<RegionCoordinates> 
<positionX>

</positionX>
<positionY>
 </positionY>
</RegionCoordinates>
</RegionCoordinatesList>
<RegionExt> 
<enabled>  </enabled>
<privacymaskName></privacymaskName>
<maskType></maskType>
</RegionExt>
</PrivacyMaskRegion>
54
Example for priavacyMask Region:
8.4.10
Input channel shelterAlarm
/Video/inputs/channels/ID/shelterAlarm
GET

Viewer
Description
It is used to get the shelter alarm configuration for a video input

channel.
Query
None
Inbound Data
None
Success Return
ShelterAlarm
PUT
Operator
Description
It is used to update the shelter alarm configuration for a video input

channel.
Query
None
Inbound Data
ShelterAlarm
Success Return
Notes:
ShelterAlarm XML Block

<ShelterAlarm version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<ShelterAlarmRegionList/> 

55
</ShelterAlarm>
8.4.11
Input channel shelterAlarm regions
/Video/inputs/channels/ID/shelterAlarm/regions
GET

Viewer
Description
It is used to get the shelter alarm regions configuration for a video

input channel.
Query
None
Inbound Data
None
Success Return
ShelterAlarmRegionList
PUT
Operator
Description
It is used to update the shelter alarm regions configuration for a video

input channel.
Query
None
Inbound Data
ShelterAlarmRegionList
Success Return
POST
Operator
Description
It is used to add a shelter alarm region for a video input channel.
Query
None
Inbound Data
ShelterAlarmRegion
Success Return
DELETE
Operator
Description
It is used to delete the shelter alarm regions configuration for a video

input channel.
Query
None
Inbound Data
None
Success Return
Notes:
ShelterAlarmRegionList XML Block

<ShelterAlarmRegionList version=1.0
<sensitivityLevel>


</sensitivityLevel>
<ShelterAlarmRegion /> 
</ShelterAlarmRegionList>

56
8.4.12
Input channel shelterAlarm region
/Video/inputs/channels/ID/shelterAlarm/regions/ID
GET
Viewer
Description
It is used to get a particular shelter alarm region configuration for a

Query
None
Inbound Data
None
Success Return
ShelterAlarmRegion
PUT
Operator
Description
It is used to update a particular shelter alarm region configuration for

Query
None
Inbound Data
ShelterAlarmRegion
Success Return
DELETE
Operator
Description
It is used to delete a particular shelter alarm region configuration for a

Query
None
Inbound Data
None
Success Return
Notes:
Region coordinates are dependent on video resolution. Only support the rectangular
region which will be drawn from four coordinates. The four points is clockwise direction,
and the beginning point is the low-left point.
Ordering of <ShelterAlarmRegion> blocks is insignificant.
ShelterAlarmRegion XML Block
<ShelterAlarmRegion version=1.0
<id>
</id>
<RegionCoordinates> 
<positionX>
</positionX>
<positionY>
 </positionY>
</ShelterAlarmRegion>

57
8.4.13
Input channel osdDatetime
/Video/inputs/channels/ID/osdDatetime
GET
Viewer
Description
It is used to get the OSD configuration for a video input channel.
Query
None
Inbound Data
None
Success Return
OsdDatetime
PUT
Operator
Description
It is used to update the OSD configuration for a video input channel.
Query
None
Inbound Data
OsdDatetime
Success Return
Notes:

<type> is the type of the year month day and should be:
0: XXXX-XX-XX Y-M-D
1: XX-XX-XXXX M-D-Y
4: XX-XX-XXXX D-M-Y
<displayWeek> means display the week or not.
<attribute> is the configuration of the OSD, the value should be:
1: transparent, flash
2: transparent, not flash
3: not transparent, flash
4: not transparent, not flash
OsdDatetime XML Block
<OsdDatetime version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<posX>  </posX>
<posY>  </posY>
<type>  </type>
<displayWeek>  </displayWeek>
<attribute>  </attribute>
</OsdDatetime>
8.5 Audio
/Audio

58
Service v1.0
Notes:
8.5.1Channels
/Audio/channels
GET
Viewer
Description
It is used to get the audio channels configuration on an IP media

device.
Query
None
Inbound Data
None
Success Return
AudioChannelList
Notes:
Since inputs are resources that are defined by the hardware configuration of the device,
audio channels cannot be created or deleted.
AudioChannelList XML Block
<AudioChannelList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<AudioChannel/> 
</AudioChannelList>
8.5.2Channel
/Audio/channels/ID
GET
Viewer
Description
It is used to get a particular audio channel configuration on an IP

media device.
Query
None
Inbound Data
None
Success Return
AudioChannel
Notes:
<audioMode> is the duplex mode for audio transmission between the client and media
device.
<microphoneVolume> Volume control percentage for device microphone..
<speakerVolume> Volume control percentage for device speaker.
AudioChannel XML Block
<AudioChannel version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>

</id>
59
<enabled>
</enabled>
<audioMode>

</audioMode>
<microphoneEnabled> 
</microphoneEnabled>
<microphoneSource>

</microphoneSource>
<microphoneVolume> 
</microphoneVolume>
<speakerEnabled>
</speakerEnabled>
<speakerVolume>

</speakerVolume>
</AudioChannel>
For encoder, please refer to Annex B (Additional content for Encoder).
8.6 Two way audio

/TwowayAudio
Service v1.0
Notes:
8.6.1Open
/TwowayAudio/open
PUT

Operator
Description
It is used to open intercom.
Query
None
Inbound Data
None
Success Return
Notes:
8.6.2Close
/TwowayAudio/close
PUT

Operator
Description
It is used to close intercom.
Query
None
Inbound Data
None
Success Return
Notes:

60
8.6.3Send data
/TwowayAudio/sendData
PUT

Operator
Description
It is used to send the intercom data.
Query
None
Inbound Data
TwowayAudio Data
Success Return
Notes:
Example
PUT /TwowayAudio/sendData HTTP/1.1
Content-Type: audio/basic
Content-Length: xxx
\r\n
TwowayAudio Data
8.6.4Receive data
/TwowayAudio/receiveData
GET

Operator
Description
It is used to receive the intercom data.
Query
None
Inbound Data
None
Success Return
TwowayAudio Data
Notes:
Example
GET /TwowayAudio/receiveData HTTP/1.1
HTTP/1.1 200 OK
Content-Type: audio/basic
Content-Length: xxx
\r\n
TwowayAudio Data

61
8.7 Serial
/Serial
Service v1.0
Notes: Serial port service.
8.7.1Ports
/Serial/ports
GET
Viewer
Description
It is used to get the list of serial ports supported by the device.
Query
None
Inbound Data
None
Success Return
SerialPorList
Notes:
Since serial ports are resources that are defined by the hardware configuration of the
device, they cannot be created or deleted.
SerialPortList XML Block
<SerialPortList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<SerialPort/> 
</SerialPortList>
8.7.2Port
/Serial/ports/ID
GET
Viewer
Description
It is used to get the configuration of a serial port supported by the

device.
Query
None
Inbound Data
None
Success Return
SerialPort
PUT
Operator
Description
It is used to update the configuration of a serial port supported by the

device.
Query
None
Inbound Data
SerialPort
Success Return

62
Notes:
<serialPortType> set the type of port; RS232, RS485. When <id> value is 1,
<serialPortType> value is RS485. When <id> value is 3, <serialPortType> value is
RS232. <serialPortType> value can not set directly.
SerialPort XML Block
<SerialPort version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>

</id>
<enabled>

</enabled>
<serialPortType> 
</serialPortType>
<baudRate>
</baudRate>
<dataBits>
</dataBits>
<parityType>
 </parityType>
<stopBits>

</stopBits>
</SerialPort>
8.7.3 Command
/Serial/ports/ID/command
PUT
Operator
Description
It is used to send a command to a serial port.
Query
chainNo
Inbound Data
SerialCommand or Raw Data
Success Return
Notes:
If the IP device is an analog-to-digital encoder and is connected to analog PTZ-enabled

camera(s), it is the devices responsibility to relay the request to the appropriate serial
interface based on the <chainNo> tag or query string.
If the IP device is itself a PTZ-enabled digital camera, it is the devices responsibility to
address the correct serial interface for the corresponding PTZ command.
The serial command can either be encapsulated in the <command> field, in which case
the data should be encoded in hexadecimal notation, or the data can be uploaded directly
as the HTTP payload, in which case the content type should be application/octet-stream.
SerialCommand XML Block
<SerialCommand version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<chainNo>
 </chainNo>
<command>
 </command>
</SerialCommand>

63
8.7.3Transparent channel open
/Serial/ports/ID/transChanOpen
PUT
Operator
Description
It is used to open the transparent channel.
Query
None
Inbound Data
None
Success Return
Notes:
Only support RS485 transparent channel, so ID value in the Resource_URI can only be 1.
8.7.4Transparent channel close

/Serial/ports/ID/transChanClose
PUT
Operator
Description
It is used to close the transparent channel.
Query
None
Inbound Data
None
Success Return
Notes:
8.7.5Transparent channel send data

/Serial/ports/ID/transChanSendData
PUT
Operator
Description
It is used to send data on the transparent channel.
Query
None
Inbound Data
Raw Data
Success Return
Notes:
Example
64
PUT /Serial/ports/1/transChanSendData HTTP/1.1
Content-Type: application/binary; charset=UTF-8

Content-Length: xxx
\r\n
Raw Data
8.7.6Transparent channel receive data

/Serial/ports/ID/transChanRecvData
GET
Operator
Description
It is used to receive data on the transparent channel.
Query
None
Inbound Data
None
Success Return
Raw Data
Notes:
Example
GET /Serial/ports/1/transChanRecvData HTTP/1.1
HTTP/1.1 200 OK
Content-Type: application/binary; charset=UTF-8

Content-Length: xxx
\r\n
Raw Data
8.8 Security
/Security
Service v1.0
Notes:
8.8.1Users
/Security/users
65
GET
Viewer
Description
It is used to get the user list for the device.
Query
None
Inbound Data
None
Success Return
UserList
PUT
Administrator
Description
It is used to update the user list for the device.
Query
None
Inbound Data
UserList
Success Return
POST
Administrator
Description
It is used to add a user for the device.
Query
None
Inbound Data
User
Success Return
DELETE
Administrator
Description
It is used to delete the user list for the device.
Query
None
Inbound Data
None
Success Return
Notes:
A default user account, admin, must be provided. Its default password is 12345. It has
an Administrator user level, and must not be deleted.
Passwords can only be uploaded - they are never revealed during GET operations.
UserList XML Block
<UserList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<User/>

</UserList>
8.8.2User
/Security/users/ID
GET
Viewer
Description
It is used to get a particular user configuration for the device.
Query
None
Inbound Data
None
Success Return
User
PUT
Description
Administrator
It is used to update a particular user configuration for the device.

66
Query
None
Inbound Data
User
Success Return
DELETE
Administrator
Description
It is used to delete a particular user for the device.
Query
None
Inbound Data
None
Success Return
Notes:
<id> of admin account is 1. admin account must not be deleted.

User XML Block
<User version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>

</id>
<userName>
</userName>
<password>

</password>
<priority>  </priority>
<ipAddress>  </ipAddress>
<macAddress>  </macAddress>
<userLevel>  </userLevel>
</User>
8.8.3adminAccess
/Security/adminAccess
GET
Viewer
Description
It is used to get administrative access protocol for the device.
Query
None
Inbound Data
None
Success Return
AdminAccessProtocol
PUT
Administrator
Description
It is used to update administrative access protocol for the device.
Query
None
Inbound Data
AdminAccessProtocol
Success Return
Notes:
<protocol> is the protocol name for admin access, i.e. HTTP, HTTPS, etc.
AdminAccessProtocol XML Block
67
<AdminAccessProtocol version=1.0
<protocol>  </protocol>
<portNo>  </portNo>
<netClientPort></netClientPort>
</AdminAccessProtocol>
8.9 Streaming
/Streaming
Service v1.0
Notes:
8.9.1Status
/Streaming/status
GET
Administrator
Description
It is used to get a device streaming status.
Query
None
Inbound Data
None
Success Return
StreamingStatus
Notes:
This command accesses the status of all device streaming sessions.

StreamingStatus XML Block
<StreamingStatus version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<totalStreamingSessions>
 </totalStreamingSessions>
<StreamingSessionStatusList/>

</StreamingStatus>
8.9.2Channels
/Streaming/channels
GET

Viewer
Description
It is used to get the properties of streaming channels for the device.
Query
None
Inbound Data
None
Success Return
StreamingChannelList

68
PUT
Administrator
Description
It is used to update the properties of streaming channels for the

device.
Query
None
Inbound Data
StreamingChannelList
Success Return
POST
Administrator
Description
It is used to add a streaming channel for the device.
Query
None
Inbound Data
StreamingChannel
Success Return
DELETE
Administrator
Description
It is used to delete the list of streaming channels for the device.
Query
None
Inbound Data
None
Success Return
Notes:
Streaming channels may be hardwired, or it may be possible to create multiple streaming

channels per input if the device supports it. To determine whether it is possible to
dynamically create streaming channels, check the defined HTTP methods in
/Streaming/channels/description.
StreamingChannelList XML Block
<StreamingChannelList version=1.0
<StreamingChannel/> 
</StreamingChannelList>
8.9.3Channel
GET

Viewer
Description
It is used to get the properties of a particular streaming channel for

the device.
Query
None
Inbound Data
None
Success Return
StreamingChannel
PUT
Description
Administrator
It is used to update the properties of a particular streaming channel

69
for the device.

Query
None
Inbound Data
StreamingChannel
Success Return
DELETE
Administrator
Description
It is used to delete a particular streaming channel for the device.
Query
None
Inbound Data
None
Success Return
Notes:
To support multi video input devices , the streaming ID in URL should be indicate video
input channel number , so it is defined as : straming-Id + video-input-Id *100, for example :
/Streaming/channels/101 indicates the first streaming from the first video input
/Streaming/channels/202 indicates the second streaming from the second video input
For IPC, becourse of only one video input, case is simeple, it can accecpt 1 as the main
stream id , 2 as the sub-stream.
<ControlProtocolList> identifies the control protocols that are valid for this type of
streaming.
<Unicast> is for direct unicast streaming.
<Multicast> is for direct multicast streaming.
<sourcePortNo> is the unicast source port parameter for the outbound video and audio
streams, and the specific port number is device-dependant.
<destPortNo> is the multicast destination port parameter for the outbound video and
audio streams, and the specific port number is device-dependant.
<videoInputChannelID> refers to /Video/inputs/channels/ID.
<audioInputChannelID> refers to /Audio/channels/ID. It must be configured as an input
channel.
<audioResolution> is the resolution for the outbound audio stream in bits.
<SVC> enables the function to realize temporal scalability, which can drop frames from
bitstream according to actual solution.
StreamingChannel XML Block
<StreamingChannel version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>

</id>
<channelName> 
</channelName>
<enabled>
</enabled>
<Transport>

<rtspPortNo>

</rtspPortNo>
<maxPacketSize>
</maxPacketSize>
<sourcePortNo>
</sourcePortNo>
70
<ControlProtocolList>

<ControlProtocol>

<streamingTransport>

</streamingTransport>
</ControlProtocol>
</ControlProtocolList>
<Unicast>

<enabled>

</enabled>
</Unicast>
<Multicast>

<enabled>

</enabled>
<destIPAddress>

</destIPAddress>
<destPortNo>
</destPortNo>
</Multicast>
</Transport>
<Video>
<enabled>
</enabled>
<videoInputChannelID>
</videoInputChannelID>
<videoCodecType>

</videoCodecType>
<videoScanType>  </videoScanType>
<videoResolutionWidth>
</videoResolutionWidth>
<videoResolutionHeight> 
</videoResolutionHeight>
<videoQualityControlType>

</videoQualityControlType>
<constantBitRate> 
</constantBitRate>
<fixedQuality> 
</fixedQuality>
<maxFrameRate> 
</maxFrameRate>
<keyFrameInterval>  </keyFrameInterval>
<BPFrameInterval>  </BPFrameInterval>
<mirrorStatus>  </mirrorStatus>
<rotationDegree> </rotationDegree>
<snapShotImageType> </snapShotImageType>
<SVC>
<enabled> 
</enabled>
<SVC>
</Video>
<Audio>
<enabled>

</enabled>
71
<audioInputChannelID>

<audioCompressionType>

</audioCompressionType>
</Audio>
</StreamingChannel>
</audioInputChannelID>
Example: Getting Streaming Channel Properties

The following is an example of a GET on the streaming parameters of a particular channel
that has been preconfigured by the IP media device. Depending on the device, some
streaming channels may be already preconfigured or the device while other may require
that channels be manually configured before use.
GET /Streaming/channels/1 HTTP/1.1
HTTP/1.1 200 OK
Content-Length: xxx
<id>1</id>
<channelName>Input 1 H.264</channelName>
<Transport>
<rtspPortNo>554</rtspPortNo>
<maxPacketSize>1000</maxPacketSize>
<sourcePortNo>8200</sourcePortNo>
<ControlProtocol>
<streamingTransport>RTSP</streamingTransport>
</ControlProtocol>
<Unicast>
</Unicast>
<Multicast>
<destIPAddress>224.16.74.1</destIPAddress>
<destPortNo>8600</destPortNo>
</Multicast>
</Transport>
<Video>
72
<videoInputChannelID>1</videoInputChannelID>
<videoCodecType>H.264</videoCodecType>
<videoScanType>progressive</videoScanType>
<videoResolutionWidth>640</videoResolutionWidth>
<videoResolutionHeight>480</videoResolutionHeight>
<videoQualityControlType>CBR</videoQualityControlType>
<constantBitRate>3072</constantBitRate>
<fixedQuality>80</fixedQuality>
<maxFrameRate>2500</maxFrameRate>
<keyFrameInterval>25</keyFrameInterval>
<BPFrameInterval>0</BPFrameInterval>
<mirrorStatus>OFF</mirrorStatus>
<rotationDegree>180</rotationDegree>
<snapShotImageType>JPEG</snapShotImageType>
<SVC>
</SVC>
</Video>
<Audio>
<audioInputChannelID>11</audioInputChannelID>
<audioCompressionType>G.711ulaw</audioCompressionType>
</Audio>
</StreamingChannel>
Example: Getting Streaming Capabilities
GET /Streaming/channels/1/capabilities HTTP/1.1
HTTP/1.1 200 OK
Content-Length: xxx
<id opt=1,2>1</id>
<channelName min=0 max=64>Input 1 H.264</channelName>
<enabled opt=true>true</enabled>
<Transport>
<rtspPortNo min=0 max=65535 def=554>554</rtspPortNo>
<maxPacketSize opt=1000>1000</maxPacketSize>
73
<sourcePortNo min=0 max=65535 def=8200>8200</sourcePortNo>

<ControlProtocol>
<streamingTransport opt=RTSP>RTSP</streamingTransport>
</ControlProtocol>
<Unicast>
<enabled opt=true def=true>true</enabled>
</Unicast>
<Multicast>
<enabled opt=true def=true>true</enabled>
<destIPAddress min=8 max=16>224.16.74.1</destIPAddress>
<destPortNo min=0 max=65535 def=8600>8600</destPortNo>
</Multicast>
</Transport>
<Video>
<enabled opt=true>true</enabled>
<videoInputChannelID opt=1>1</videoInputChannelID>
<videoCodecType opt=H.264,MJPEG>H.264</videoCodecType>
<videoScanType opt=progressive>progressive</videoScanType>
<videoResolutionWidth opt=640*480>640</videoResolutionWidth>
<videoResolutionHeight opt=640*480>480</videoResolutionHeight>
<videoQualityControlType opt=CBR,VBR>CBR</videoQualityControlType>
<constantBitRate min=32 max=4000>3072</constantBitRate>
<fixedQuality opt=1,20,40,60,80,100>80</fixedQuality>
<maxFrameRate
opt=2500,2200,2000,1800,1600,1500,1200,1000,800,600,400,200,100,50,25,
12,6>2500</maxFrameRate>
<keyFrameInterval min=1, max=400>25</keyFrameInterval>
<BPFrameInterval opt=0, 1, 2>0</BPFrameInterval>
<mirrorStatus opt="OFF,UpToDown,LeftToRight">OFF</mirrorStatus>
<rotationDegree opt="0,180">180</rotationDegree>
<snapShotImageType opt=JPEG def=JPEG>JPEG</snapShotImageType>
<SVC>
<enabled opt="ture,false">true</enabled>
</SVC>
</Video>
<Audio>
<enabled opt=true,false>true</enabled>
<audioInputChannelID opt=11,12>11</audioInputChannelID>
<audioCompressionType opt=G.711ulaw>G.711ulaw</audioCompressionType>
</Audio>
</StreamingChannel>
74
8.9.4Dynamic capabilities
/Streaming/channels/ID/dynamicCap
GET
Description
Get dynamic capabilities, different resolutions have different frame

rates; different audio compression types have different audio bit rate.
Query
None
Inbound Data
None
Success Return
DynamicCap
Notes:
DynamicCap XML Block

<DynamicCap version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<ResolutionAvailableDscriptorList>
<ResolutionAvailableDscriptor>
<videoResolutionWidth>  </videoResolutionWidth>
<videoResolutionHeight>
 </videoResolutionHeight>
<supportedFrameRate>  </supportedFrameRate>
</ResolutionAvailableDscriptor>
</ResolutionAvailableDscriptorList>
<AudioDscriptorList>

</AudioDscriptorList>
</DynamicCap>
Example: Getting the Dynamic Capabilities
GET /Streaming/Channels/101/dynamicCap HTTP/1.1
HTTP/1.1 200 OK
Content-Length: xxx
<?xml version="1.0" encoding="UTF-8"?>
<DynamicCap version="2.0" xmlns="http://www.hikvision.org/ver20/XMLSchema">
75
<ResolutionAvailableDscriptorList>
<supportedFrameRate>2500,6,12,25,50,100,200,400,600,800,1000,1200,1500,16
00,1800,2000,2200</supportedFrameRate>
</ResolutionAvailableDscriptorList>
<AudioDscriptorList>
<audioCompressionType
SupportedAudioBitRate="32,64,128">MP2L2</audioCompressionType>
</AudioDscriptorList>
</DynamicCap>
8.9.5Channel status
/Streaming/channels/ID/status
GET

Administrator
Description
It is used to get the list of streaming sessions associated with a

particular channel.
Query
None
Inbound Data
None
Success Return
StreamingSessionStatusList
Notes:
StreamingSessionStatusList XML Block

<StreamingSessionStatusList version=1.0
<StreamingSessionStatus>
76
<clientAddress> 

<ipAddress>
</clientAddress>
</StreamingSessionStatus>
</StreamingSessionStatusList>
</ipAddress>
8.9.6Picture
/Streaming/channels/ID/picture
GET
Operator
Description
It is used to get a snapshot of the current image.
Query
videoResolutionWidth
videoResolutionHeight
snapShotImageType
Inbound Data
None
Success Return
Picture over HTTP
Notes:
All devices must support <snapShotImageType> of JPEG.

Only support the main stream channel snapshot.
To determine the format of the picture returned, either the parameters in <Video> or the
query string values are used, or, if the Accept: header field is present in the request and
the server supports it, the picture is returned in that format.
For supported values, query /Streaming/channels/ID/picture/capabilities.
Examples:
GET /Streaming/channels/1/picture?snapShotImageType=JPEG
GET /Streaming/channels/1/picture
Accept: image/jpeg
8.9.7Request keyframe
/Streaming/channels/ID/requestKeyFrame
PUT

Operator
Description
It is used to request that the device issue a key frame on a particular

channel.
Query
None
Inbound Data
None

77
Success Return
Notes:
The key frame that is issued should include everything necessary to initialize a video
decoder, i.e. parameter sets for H.264.
8.10 Motion Detection

/MotionDetection
Service
GET
v1.0
Viewer
Description
It is used to get the motion detection configuration for all video input
channels.
Query
None
Inbound Data
None
Success Return
MotionDetectionList
Notes:
If motion detection is supported by the device, a motion detection ID will be allocated for
each video input channel ID. The motion detection ID must correspond to the video input
channel ID.
MotionDetectionList XML Block
<MotionDetectionList version=1.0
<MotionDetection/>

</MotionDetectionList >
8.10.1
One channel motion detection
/MotionDetection/ID
GET

Viewer
Description
It is used to get the motion detection configuration for a video input

channel.
Query
None
Inbound Data
None
Success Return
MotionDetection
PUT
Operator
Description
It is used to udpate the motion detection configuration for a video

input channel.
Query
None

78
Inbound Data
MotionDetection
Success Return
Notes:
Note that the ID used here MUST correspond to the video input ID.
The interface supports grid-based motion detection.
Grid-based motion detect divides the image into a set of fixed bins that delimit the motion
detection area boundaries.
MotionDetection XML Block
<MotionDetection version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>
</id>
<enabled>
</enabled>
<regionType>

</regionType>
<Grid>

<rowGranularity>
 </rowGranularity>
<columnGranularity>  </columnGranularity>
</Grid>
<MotionDetectionRegionList/> 
</MotionDetection>
8.10.2
Motion detection regions
/MotionDetection/ID/regions
GET

Viewer
Description
It is used to get the motion detection regions configuration for a video

input channel.
Query
None
Inbound Data
None
Success Return
MotionDetectionRegionList
PUT
Operator
Description
It is used to update the motion detection regions configuration for a

Query
None
Inbound Data
MotionDetectionRegionList
Success Return
POST
Operator
Description
It is used to add a motion detection region for a video input channel.
Query
None
Inbound Data
MotionDetectionRegion
Success Return

79
DELETE
Operator
Description
It is used to delete the motion detection regions configuration for a

Query
None
Inbound Data
None
Success Return
Notes:
All motion detection regions share a sensitivity level.

It is possible to define mask regions that are subtracted from other regions.
MotionDetectionRegionList XML Block
<MotionDetectionRegionList version=1.0
<sensitivityLevel>


</sensitivityLevel>
<MotionDetectionRegion/> 
</MotionDetectionRegionList>
8.10.3
Motion detection region
/MotionDetection/ID/regions/ID
GET

Viewer
Description
It is used to get a particular motion detection region configuration for

Query
None
Inbound Data
None
Success Return
PUT
Operator
Description
It is used to update a particular motion detection region configuration

for a video input channel.
Query
None
Inbound Data
Success Return
DELETE
Operator
Description
It is used to delete a particular motion detection region configuration

for a video input channel.
Query
None
Inbound Data
None

80
Success Return
Notes:
The region detection coordinate space depends on the value of <regionType>.

Only support the rectangular region which will be drawn from four coordinates. The four
points is clockwise direction, and the beginning point is the low-left point.
MotionDetectionRegion XML Block
<MotionDetectionRegion version=1.0
<id>
 </id>
<enabled>
<maskEnabled>
 </maskEnabled>
<RegionCoordinates> 
<positionX>
 </positionX>
<positionY>
 </positionY>
</MotionDetectionRegion>
8.10.4
Motion Detection Example
Set up Motion Detection

The following command configures two rectangular detection regions, with one masked
region on video input channel ID 1. Example assumes a resolution of 1600x1200 and a
grid motion detection algorithm:
- Motion detection is enabled with a granularity of a 22x18 grid this means the
detection region coordinates will ultimately be defined by a grid of 396 regions.
For a resolution of 1600x1200, this means that each granule will be 1600/22 x
1200/18 pixels. (If a coordinate doesnt exactly match the configured granularity,
it should be mapped internally to the nearest possible point).
- Two detection regions are defined, the second containing an inner/overlapping
region that is disabled. Region 1 occupies the bottom-left 16 granules. Region
2 occupies the middle 16 granules, with the top-right-most corner granule (region
3) disabled by use of the <maskEnabled> tag.

81
1200
Mask Region 3
Region 2
Region 1
1600
PUT /MotionDetection/1 HTTP/1.1

Content-Length: xxx
<MotionDetection version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>1</id>
<MotionDetectionRegionList>
<sensitivityLevel>2</sensitivityLevel>
<MotionDetectionRegion>
<id>1</id>
<maskEnabled>false</maskEnabled>
<RegionCoordinatesList>
<RegionCoordinates>
<positionX>0</positionX>
<positionY>0</positionY>
<RegionCoordinates>
<RegionCoordinates>
82
<RegionCoordinates>
<id>2</id>
<maskEnabled>false</maskEnabled>
<RegionCoordinates>
<RegionCoordinates>
<RegionCoordinates>
<RegionCoordinates>
<id>3</id>
<maskEnabled>true</maskEnabled>
<RegionCoordinates>
<RegionCoordinates>
<RegionCoordinates>
83
<RegionCoordinates>
</MotionDetection>
8.10.5
/MotionDetectionExt/<ID>
/MotionDetectionExt/ID
Service v2.0
GET
Description
channels.
Query
None
Inbound Data
None
Success Return
MotionDetectionExt
PUT
Description

input channel.
Query
None
Inbound Data
MotionDetectionExt
Success Return
ResponseStatus
Notes:
channel ID.
<activeMode> indicates current effective motion detection mode, <activeMode> will
switch to Normal mode automatically when using /MotionDetection/<ID>/regions to
configure motion detection; <activeMode> will switch to expert mode automatically when
using /MotionDetectionExt/<ID>
MotionDetectionExt XML Block

<MotionDetectionExt version=1.0
<enabled> 
</enabled>
84
<minObjectSize>

</minObjectSize>
<maxObjectSize>

</maxObjectSize>
<ROI>

<minHorizontalResolution>  </minHorizontalResolution>
<minVerticalResolution>  </minVerticalResolution>
</ROI>
<highlightsenabled> 
</highlightsenabled>
<MotionDetectionSwitch/>
<activeMode> 
</MotionDetectionExt>
8.10.6
/MotionDetectionExt/<ID>/switch
/MotionDetectionExt/ID/switch
GET
Description
It is used to get the motion detection switch day and night settings.
Query
None
Inbound Data
None
Success Return
MotionDetectionSwitch
PUT
Description
It is used to udpate the motion detection switch day and night

settings.
Query
None
Inbound Data
MotionDetectionSwitch
Success Return
ResponseStatus
Notes:
channel ID.
MotionDetectionSwitch XML Block
<MotionDetectionSwitch version=1.0
<type>
85


</type>
<Schedule> 
<scheduleType><!req,xs:string,day,night></scheduleType>
<TimeRange> 
<beginTime>  </beginTime>
<endTime>  </endTime>
</TimeRange>
</Schedule>
</MotionDetectionSwitch>
8.10.7
/MotionDetectionExt/<ID>/regions
/MotionDetectionExt/ID/regions
GET
8.10.8
/MotionDetectionExt/<ID>/regions/<ID>
/MotionDetectionExt/ID/regions/ID
GET
Description
channels.
Query
None
Inbound Data
None
Success Return
PUT
Description

input channel.
Query
None
Inbound Data
Success Return
ResponseStatus
Notes:

86
channel ID.
MotionDetectionRegion XML Block
<MotionDetectionRegion version=1.0
<id> </id>
<maskEnabled>
 </maskEnabled>
<daySensitivityLevel> 

</daySensitivityLevel>
<nightSensitivityLevel> 
</nightSensitivityLevel>
<sensitivityLevel> 
</sensitivityLevel>
<dayObjectSize> 
</dayObjectSize>
<nightObjectSize> 
</nightObjectSize>
<objectSize> 
</objectSize>
<detectionThreshold> 

</detectionThreshold>

<RegionCoordinates> 
<positionX>
 </positionX>
<positionY>
 </positionY>

87
8.11 Event
/Event
Service
GET
v1.0
Viewer
Description
It is used to get the configuration of the device event behavior,

scheduling and notifications.
Query
None
Inbound Data
None
Success Return
EventNotification
PUT
Operator
Description
It is used to udpate the configuration of the device event behavior,

scheduling and notifications.
Query
None
Inbound Data
EventNotification
Success Return
Notes:
The event trigger list defines the set of device behaviors that trigger events.
The event schedule defines when event notifications are active.
The event notification methods define what types of notification (e-mail) are supported.
EventNotification XML Block
<EventNotification version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<EventTriggerList/>

<EventSchedule/>

<EventNotificationMethods/> 
</EventNotification>
8.11.1
Triggers
/Event/triggers
GET
Viewer
Description
It is used to get the list of event triggers.
Query
None
Inbound Data
None
Success Return
EventTriggerList
PUT
Operator
Description
It is used to update the list of event triggers.
Query
None
Inbound Data
EventTriggerList

88
Success Return
POST
Operator
Description
It is used to add an event trigger.
Query
None
Inbound Data
EventTrigger
Success Return
DELETE
Operator
Description
It is used to delete the list of event triggers.
Query
None
Inbound Data
None
Success Return
Notes:
Event triggering defines how the device reacts to particular events, such as video loss or
motion detection.
EventTriggerList XML Block
<EventTriggerList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<EventTrigger/> 
</EventTriggerList>
8.11.2
Trigger
/Event/triggers/ID
GET
Viewer
Description
It is used to get a particular event trigger configuration.
Query
None
Inbound Data
None
Success Return
EventTrigger
PUT
Operator
Description
It is used to update a particular event trigger configuration.
Query
None
Inbound Data
EventTrigger
Success Return
DELETE
Operator
Description
It is used to delete a particular event trigger.
Query
None
Inbound Data
None
Success Return
Notes:

89
An event trigger determines how the device reacts when a particular event is detected.
The following types are supported:
IO: trigger when an input IO port changes state.
VMD: trigger on video motion detection.
Video loss: trigger when the input video signal cannot be detected.
Shelter alarm: trigger when shelter is set.
The ID in the URI is the sequence number of a trigger , the max value of <id> is depend
on device. The first trigger id is 1.
<inputIOPortID> is only required if <eventType> is IO.
The trigger ID in URL is defined as :
1 to N are assigned for alarm input port 1 to N
N+1 is assigned for VMD event
N+2 is assigned for video-loss event
N+3 is assigned for Shelter alarm event
N+4 is assigned for field detection event
N+5 is assigned for audio exception detection event
N+6 is assigned for defocus detection event
N+7 is assigned for scene change detection event
N+8 is assigned for face detection
Example: For an IPC that with three alarm input ports, trigger 1 is alarm input 1 , trigger 3
is for alarm input 3, trigger 4 is for VMD, trigger 5 is for Video loss , trigger 6 is for shelter
alarm.
<EventTrigger version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>

</id>
<eventType>
 </eventType>
<eventDescription>
</eventDescription>
<inputIOPortID>
</inputIOPortID>
<EventTriggerNotificationList/> 
</EventTrigger>
8.11.3
Trigger notifications
/Event/triggers/ID/notifications
GET
90

Viewer
Description
It is used to get the list of notification methods and behaviors for an

event trigger.
Query
None
Inbound Data
None
Success Return
EventTriggerNotificationList
PUT
Operator
Description
It is used to update the list of notification methods and behaviors for

an event trigger.
Query
None
Inbound Data
EventTriggerNotificationList
Success Return
POST
Operator
Description
It is used to add a notification method and behavior for an event

trigger.
Query
None
Inbound Data
EventTriggerNotification
Success Return
DELETE
Operator
Description
It is used to delete the list of notification method and behavior for an

event trigger.
Query
None
Inbound Data
None
Success Return
Notes:
This section determines the kinds of notifications that are supported for a particular event
trigger and their recurrences and behaviors.
EventTriggerNotificationList XML Block
<EventTriggerNotificationList version=1.0
<EventTriggerNotification/> 
</EventTriggerNotificationList>
8.11.4
Trigger notification
/Event/triggers/ID/notifications/ID
GET

Viewer
Description
It is used to get a particular notification method and behavior for an

event trigger.
Query
None

91
Inbound Data
None
Success Return
PUT
Operator
Description
It is used to update a particular notification method and behavior for

an event trigger.
Query
None
Inbound Data
Success Return
DELETE
Operator
Description
It is used to delete a particular notification method and behavior for

an event trigger.
Query
None
Inbound Data
None
Success Return
Notes:
The first ID in the URI is the sequence number of a trigger , the max value of <id> is
depend on device. The first trigger id is 1.
The second ID in the URI is the sequence number a notification , the max value of <id>
is depend on device. The first notification id is 1.
<outputIOPortID> is only required if the <notifiocationMethod> is IO.
<ptzAction> is only required if the <notifiocationMethod> is PTZ.
EventTriggerNotification XML Block
<EventTriggerNotification version=1.0
<id>
</id>
<notificationMethod></notificationMetho
d>
<notificationRecurrence> 
</notificationRecurrence>
<outputIOPortID>

</outputIOPortID>
<ptzAction> 
<ptzChannelID>  </ptzChannelID>
<actionName>  </actionName>
<actionNum> 
<TimeBlock>
<dayOfWeek>

</dayOfWeek>
<TimeRange>

<beginTime>
 </beginTime>
<endTime>
 </endTime>
</TimeRange>
</TimeBlock>
</TimeBlockList>
</EventSchedule>
8.11.6
Schedule/ID
/Event/Schedule/ID
GET
Viewer
Description
It is used to get event schedules.
Query
None

93
Inbound Data
None
Success Return
EventSchedule
PUT
Operator
Description
It is used to update event schedules.
Query
None
Inbound Data
EventSchedule
Success Return
Notes:
This is a new resource, may be some old firmware isnt supported.

Old url is : /Custom/HIKCGI/Event/schedule/ID
New firmware will support both of them.
ID is defined as TypeName. If the event type is IO, the ID is IO_IN_PortNumber/ the ID is
IO_OUT_PortNumber.
Examples :
VMD : Video Motion Detection
videoloss : Video Loss
shelteralarm : Shelter Alarm
fielddetection : Field Detection
audioexception : Audio Exception
scenechangedetection : Scene Change Detection
IO_ IN _1 :the first IO input port
IO_OUT_2 : the second IO output port
EventSchedule XML Block
<eventType>


</eventType>
<inputIOPortID>
<outputIOPortID>

</inputIOPortID>
</inputIOPortID>

<TimeBlock>
<dayOfWeek>
</dayOfWeek>
<TimeRange>
<beginTime>
<endTime>





94
</beginTime>
</endTime>
</TimeRange>
</TimeBlock>
</TimeBlockList>
</EventSchedule>
8.11.7
Notification
/Event/notification
GET
Viewer
Description
It is used to get event notifications configuration.
Query
None
Inbound Data
None
Success Return
EventNotificationMethods
PUT
Operator
Description
It is used to update event notifications configuration.
Query
None
Inbound Data
EventNotificationMethods
Success Return
Notes:
E-mail notification type is supported.

E-mail: a mail with relevant information is sent in an e-mail to a list of servers.
EventNotificationMethods XML Block
<EventNotificationMethods version=1.0
<MailingNotificationList/>

<EmailFormat>

<senderEmailAddress>
 </senderEmailAddress>
<receiverEmailAddress>
 </receiverEmailAddress>
</EmailFormat>
</EvenNotificationMethods>
8.11.8
Mails notification
/Event/notification/mailing
GET
Viewer
Description
It is used to get the list of E-mail notifications.
Query
None

95
Inbound Data
None
Success Return
MailingNotificationList
PUT
Operator
Description
It is used to update the list of E-mail notifications.
Query
None
Inbound Data
MailingNotificationList
Success Return
POST
Operator
Description
It is used to add an E-mail notification.
Query
None
Inbound Data
MailingNotification
Success Return
DELETE
Operator
Description
It is used to delete the list of E-mail notifications.
Query
None
Inbound Data
None
Success Return
Notes:
When the notification is triggered, an e-mail with relevant information is mailed to the each
of the addresses in the mailing list.
MailingNotificationList XML Block
<MailingNotificationList version=1.0
<MailingNotification/>

</MailingNotificationList>
8.11.9
Mail notification
/Event/notification/mailing/ID
GET
Viewer
Description
It is used to get a particular E-mail notification configuration.
Query
None
Inbound Data
None
Success Return
MailingNotification
PUT
Operator
Description
It is used to update a particular E-mail notification configuration.
Query
None
Inbound Data
MailingNotification

96
Success Return
DELETE
Operator
Description
It is used to delete a particular E-mail notification.
Query
None
Inbound Data
None
Success Return
Notes:
Depending on the value of <addressingFormatType>, either the <hostName> or the IP

address fields will be used to locate the SMTP server.
<authenticationMode> determines the authentication requirements for sending an email
from the device.
<portNo> is the port number of the SMTP server entry.
<accountName> is the user account name for the SMTP server.
MailingNotification XML Block
<MailingNotification version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>
</id>
<authenticationMode>

</authenticationMode>

<hostName>
</hostName>
<ipAddress>
</ipAddress>
<portNo>
</portNo>
<accountName>
 </accountName>
<password>
 </password>
<attachmentEnable>  </attachmentEnable>
<attachmentInterval>  </attachmentInterval>
<sslEnable>  </sslEnable>
<EmailFormatExt> 
<senderEmailAddress> 
</senderEmailAddress>
<receiverEmailAddressList>
<receiverEmailAddress>
<id>
</id>
<EmailAddress>  </EmailAddress>
</receiverEmailAddress>
</receiverEmailAddressList>
</EmailFormatExt>
</MailingNotification>

97
8.11.10 HTTP Hosts

/Event/notification/httpHost
General Resource
v2.0
GET
Description
It is used to get the configuration of e-mail.
Query
None
Inbound Data
None
Success Return
HttpHostNotificationList
PUT
Description
It is used to set the configuration of e-mail.
Query
None
Inbound Data
HttpHostNotificationList
Success Return
ResponseStatus
Notes:
HttpHostNotificationList XML Block

<HttpHostNotificationList
<HttpHostNotification/> 
</HttpHostNotificationList>
version=1.0
8.11.11 HTTP Host

/Event/notification/httpHost/ID
General Resource
v2.0
GET
Description
It is used to get the configuration of a particular e-mail.
Query
None
Inbound Data
None
Success Return
HttpHostNotification
PUT
Description
It is used to set the configuration of a particular e-mail.
Query
None
Inbound Data
HttpHostNotification
Success Return
ResponseStatus
Notes:
HttpHostNotification XML Block

<HttpHostNotification
<id> 
</id>
98
version=1.0
<url>  </url>

<protocolType> 
<parameterFormatType>

</parameterFormatType>

<hostName>  </hostName>
<ipAddress>  </ipAddress>
<ipv6Address>  </ipv6Address>
<portNo>  </portNo>
<userName>  </userName>
<password>
 </password>
<httpAuthenticationMethod>

</httpAuthenticationMethod>
</HttpHostNotification>
</protocolType>
8.11.12 Notification alertStream

/Event/notification/alertStream
GET

Viewer
Description
It is used to get the event notification data stream through HTTP

server push.
Query
None
Inbound Data
None
Success Return
Stream of <EventNotificationAlert>
Notes:
This function is used to get an event notification alert stream from the media device via
HTTP or HTTPS. This function does not require that a client/VMS system be added as an
HTTP(S) destination on the media device. Instead, the client/VMS system can call this
API to initialize a stream of event information from the device. In other words, a
connection is established with the device when this function is called, and stays open to
constantly receive event notifications.
This API uses HTTP server-push with the MIME type multipart/mixed defined in RFC
2046.
<protocol> is the protocol name, i.e. HTTP or HTTPS.
<channelID> is present for video and analytics events.
<activePostCount> is the sequence number of current notification for this particular event.
It starts at 1. Useful for recurring notifications of an event. Each event maintains a
99
separate post count.

EventNotificationAlert XML Block
<EventNotificationAlert version=1.0
<ipAddress>
</ipAddress>
<portNo>
</portNo>
<protocol>
</protocol>
<macAddress>
 </macAddress>
<channelID>
</channelID>
<dateTime>
 </dateTime>
<activePostCount> 
</activePostCount>
<eventType>  </eventType>
<eventState>
 </eventState>
<eventDescription> 
</eventDescription>
<inputIOPortID> 
</inputIOPortID>
<DetectionRegionList>

<DetectionRegionEntry>

<regionID>
</regionID>
<sensitivityLevel>
 </sensitivityLevel>
</DetectionRegionEntry>
</DetectionRegionList>
</EventNotificationAlert>
Example
The following is an example of an HTTP event stream that pushes a VMD event from
video channel 1.
GET /Event/notification/alertStream HTTP/1.1
HTTP/1.1 200 OK
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=<boundary>
--<boundary>
Content-Length: xxx
<EventNotificationAlert version=1.0
<portNo>80</portNo>
<protocol>HTTP</protocol>
100
<macAddress>01:17:24:45:D9:F4</macAddress>
<channelID>1</channelID>
<dateTime>2009-11-14T15:27Z</dateTime>
<activePostCount>1</activePostCount>
<eventType>VMD</eventType>
<eventState>active</eventState>
<eventDescription>Motion alarm</eventDescription>
<DetectionRegionList>
<DetectionRegionEntry>
<regionID>2</regionID>
<sensitivityLevel>4</sensitivityLevel>
</DetectionRegionEntry>
</DetectionRegionList>
</EventNotificationAlert>
--<boundary>
8.11.13 Event Triggering Examples

Example: Trigger Events on IO Port
The command below enables detection for input port 1. When the input signal is detected
according to <inputIOPortID>, two event notification responses are used output port 2
will be triggered for the duration of the input signal detection, and an SMTP server will be
notified with the E-mail Event Notification Alert. The behavior of this notification is as
follows:
- A SMTP notification is sent at detection time, and every some seconds after while
the signal is present. This is denoted by the <notificationRecurrence> tags. These
APIs will have an <eventState> of active.
- When the input port 1 signal detection stops, one last E-mail notification is sent to
the server with an <eventState> of active.
- After the signal detection stops for input port 1, the device will wait some seconds
before starting to detect the signal again for this port.
PUT /Event/triggers HTTP/1.1
Content-Length: xxx
<id>1</id> 
<EventTriggerNotificationList>
101
<EventTriggerNotification>
<id>1</id> 
<EventTriggerNotification>
<id>2</id> 
</EventTriggerNotificationList>
</EventTrigger>
Example: Schedule event detection and triggering
The command below schedules event detection and triggering from 7:00 am to 5:00 pm.
every Tuesday.
PUT /Event/schedule HTTP/1.1
Content-Length: xxx
<TimeBlockList>
<TimeBlock>
<dayOfWeek>2</dayOfWeek>
<TimeRange>
<beginTime>07:00:00</beginTime>
<endTime>17:00:00</endTime>
</TimeRange>
</TimeBlock>
</TimeBlockList>
</EventSchedule>
8.12 PTZ
/PTZ
Service v1.0
Notes: PTZ control service.
8.12.1
Channels
/PTZ/channels
GET
Description
Viewer
It is used to get the list of PTZ channels for the device.

102
Query
None
Inbound Data
None
Success Return
PTZChannelList
PUT
Operator
Description
It is used to update the list of PTZ channels for the device.
Query
None
Inbound Data
PTZChannelList
Success Return
POST
Operator
Description
It is used to add a PTZ channel for the device.
Query
None
Inbound Data
PTZChannel
Success Return
DELETE
Operator
Description
It is used to delete the list of PTZ channels for the device.
Query
None
Inbound Data
None
Success Return
Notes:
PTZ channels may be hardwired, or it may be possible to create channels if the device
supports it. To determine whether it is possible to dynamically PTZ channels, check the
defined HTTP methods in /PTZ/channels/description.
PTZChannelList XML Block
<PTZChannelList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<PTZChannel/>

</PTZChannelList>
8.12.2
Channel
/PTZ/channels/ID
GET
Viewer
Description
It is used to get a particular PTZ channel configuration for the device.
Query
None
Inbound Data
None
Success Return
PTZChannel
PUT
Description
Operator
It is used to update a particular PTZ channel configuration for the
device.

103
Query
None
Inbound Data
PTZChannel
Success Return
DELETE
Operator
Description
It is used to delete a particular PTZ channel for the device.
Query
None
Inbound Data
None
Success Return
Notes:
<videoInputID> links the PTZ channel to a video channel.

<controlProtocol> indicates the control protocol to be used for PTZ.
PTZChannel XML Block
<PTZChannel version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<videoInputID>
 </videoInputID>
<controlProtocol>  </controlProtocol>
<controlAddress>
 </controlAddress>
<PresetIDList> <! opt -->
<PresetID> <! opt -->
<id>  </id>
</PresetID>
</PresetIDList >
<PatrolIDList> <! opt -->
<PatrolID> <! opt -->
</PatrolID>
</PatrolIDList >
<PatternIDList> <! opt -->
<PatternID> <! opt -->
</PatternID>
</PatternIDList>
</PTZChannel>

104
8.12.3
Patrols
/PTZ/channels/ID/patrols
GET
Viewer
Description
It is used to get the list of patrols for a PTZ channel.
Query
None
Inbound Data
None
Success Return
PTZPatrolList
Notes:
PTZPatrolList XML Block

<PTZPatrolList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<PTZPatrol> 
</ PTZPatrolList >
8.12.4
Patrol
/PTZ/channels/ID/patrols/ID
GET
Viewer
Description
It is used to get a particular patrol configuration for a PTZ channel.
Query
None
Inbound Data
None
Success Return
PTZPatrol
PUT
Operator
Description
It is used to update a particular patrol configuration for a PTZ

channel.
Query
None
Inbound Data
PTZPatrol
Success Return
Notes:
PTZPatrol XML Block

<PTZPatrol version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<PatrolPointList /> <!opt -->
</ PTZPatrol>

105
8.12.5
Patrol keyPoints
/PTZ/channels/ID/patrols/ID/keyPoints
GET

Viewer
Description
It is used to get the list of key points of a particular patrol for a PTZ
channel.
Query
None
Inbound Data
None
Success Return
PatrolPointList
PUT
Operator
Description
It is used to update the list of key points of a particular patrol for a

PTZ channel.
Query
None
Inbound Data
PatrolPointList
Success Return
POST
Operator
Description
It is used to add a key point of a particular patrol for a PTZ channel.
Query
None
Inbound Data
PatrolPoint
Success Return
DELETE
Operator
Description
It is used to delete the list of key points of a particular patrol for a PTZ
channel.
Query
None
Inbound Data
None
Success Return
Notes:
PatrolPointList XML Block

<PatrolPointList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<PatrolPoint /> <!opt -->
</PatrolPointList>
8.12.6
Patrol keyPoint
/PTZ/channels/ID/patrols/ID/keyPoints/ID
GET
Description

Viewer
It is used to get a particular key point of a particular patrol for a PTZ

channel.

106
Query
None
Inbound Data
None
Success Return
PatrolPoint
PUT
Operator
Description
It is used to update a particular key point of a particular patrol for a

PTZ channel.
Query
None
Inbound Data
PatrolPoint
Success Return
DELETE
Operator
Description
It is used to delete a particular key point of a particular patrol for a

PTZ channel.
Query
None
Inbound Data
None
Success Return
Notes:
<presetNo> is Presets series number.

<speed> is Patrol speed.
<dwellTime> is the stay time for the patrol point, the unit is second
PatrolPoint XML Block
<PatrolPoint version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<presetNo>  </ presetNo>
<speed> <!opt, xs:integer --> </speed>
<dwellTime> <!opt, xs:integer --> </dwellTime>
</PatrolPoint>
8.12.7
PTZControl
/PTZ/channels/ID/PTZControl
PUT

Operator
Description
It is used to control PTZ.
Query
command
presetNo
patrolNo
mode
speed
Inbound Data
None
Success Return

107
Notes:
The value of command is:

LIGHT: Light
WIPER: Wiper
FAN: Fan
HEATER: Heater.
AUX1: auxiliary equipment 1.
AUX2: auxiliary equipment 2
SET_PRESET: Set preset
CLE_PRESET: Clear preset.
ZOOM_IN: Zoom in the specified speed.
ZOOM_OUT: Zoom out in the specified speed.
FOCUS_NEAR: focus near in the specified speed.
FOCUS_FAR: focus far in the specified speed.
IRIS_OPEN: IRIS is open in the specified speed
IRIS_CLOSE: IRIS is cloesd in the specified speed
TILT_UP: PTZ is tilt up in the specified speed
TILT_DOWN: PTZ is tilt down in the specified speed
PAN_LEFT: PTZ is pan left in the specified speed
PAN_RIGHT: PTZ is pan right in the specified speed
UP_LEFT: PTZ is up-left in the specified speed
UP_RIGHT: PTZ is up-right in the specified speed
DOWN_LEFT: PTZ is down-left in the specified speed
DOWN_RIGHT: PTZ is down-right in the specified speed
PAN_AUTO: PTZ scans pan with the specified speed.
MEM_PATTERN: memory pattern.
RUN_PATTERN: Start pattern.
PATROL: patrol.
GOTO_PRESET: Go to preset.
mode value is start and stop. It indicates the start or stop of some actions for PTZ,
or the turn on or turn off of external equipment power for PTZ. The default is start.
In addition to the SET_PRESET, CLE_PRESET, RUN_PATTERN and
GOTO_PRESET command, all commands require the mode query parameters.
speed range is 1-7.
When the command is ZOOM_IN, ZOOM_OUT, FOCUS_NEAR, FOCUS_FAR,
IRIS_OPEN, or IRIS_CLOSE, the default is 1.
When the command is TILT_UP, TILT_DOWN, PAN_LEFT, PAN_RIGHT,
UP_LEFT, UP_RIGHT, DOWN_LEFT, DOWN_RIGHT, PAN_AUTO, the default is
3.
Examples:
108
/PTZ/channels/ID/PTZControl?command=UP_LEFT&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=GOTO_PRESET&presetno=1&speed=1
/PTZ/channels/ID/PTZControl?command=TILT_UP&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=TILT_DOWN&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=PAN_LEFT&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=PAN_RIGHT&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=UP_LEFT&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=UP_RIGHT&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=DOWN_LEFT&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=DOWN_RIGHT&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=PAN_AUTO&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=LIGHT
/PTZ/channels/ID/PTZControl?command=WIPER
/PTZ/channels/ID/PTZControl?command=ZOOM_IN&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=ZOOM_OUT&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=FOCUS_NEAR&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=FOCUS_FAR&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=IRIS_OPEN&speed=1&mode=start
/PTZ/channels/ID/PTZControl?command=IRIS_CLOSE&speed=1&mode=start
8.13 PTZCtrl
/PTZCtrl
Service v1.0
Notes: PTZCtrl control service.
8.13.1
/PTZCtrl/channels
/PTZCtrl/channels
GET
Viewer
Description
It is used to get the list of PTZ channels for the device
Query
None
Inbound Data
None
Success Return
PTZChannelList
PUT
Operator
Description
It is used to update the list of PTZ channels for the device.
Query
None
Inbound Data
PTZChannelList
Success Return
POST

109
Operator
It is used to add a PTZ channel for the device.
Description
Query
None
Inbound Data
PTZChannel
Success Return
DELETE
Administrator
Description
It is used to delete the list of PTZ channels for the device.
Query
None
Inbound Data
None
Success Return
Notes:
PTZ channels may be hardwired, or it may be possible to create channels if the device
supports it. To determine whether it is possible to dynamically PTZ channels, check the
defined HTTP methods in /PTZCtrl/channels/description.
PTZChannelList XML Block
<PTZChannelList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<PTZChannel/>

</PTZChannelList>
8.13.2
/PTZCtrl/channels/<ID>
/PTZCtrl/channels/<ID>
GET
Viewer
Description
It is used to get a particular PTZ channel configuration for the device.
Query
None
Inbound Data
None
Success Return
PTZChannel
PUT
Operator
Description
It is used to update a particular PTZ channel configuration for the

device.
Query
None
Inbound Data
PTZChannel
Success Return
DELETE
Operator
Description
It is used to delete a particular PTZ channel on a device.
Query
None
Inbound Data
None
Success Return

110
Notes:
<videoInputID> links the PTZ channel to a video channel.

<presetSpeed> indicates the movement speed level about calling preset
<autoScanSpeed> indicates the movement speed level about park function
<keyPadControlSpeed> indicates the movement speed level to be controlled by keyboard
<controlProtocol> indicates the control protocol to be used for PTZ.
< controlAddress> indicates the soft address (enabled means soft address is used)
<enabled> <!ro,req, xs:boolean --> </enabled>
<videoInputID>
<panMaxSpeed> <!ro,opt, xs:integer, degrees/sec --> </panMaxSpeed>
<tiltMaxSpeed> <!ro,opt, xs:integer, degrees/sec --> </tiltMaxSpeed>
<presetSpeed> <!opt, xs:integer 1..8 > </presetSpeed>
<autoPatrolSpeed>  </autoPatrolSpeed>
<keyBoardControlSpeed>
 </controlProtocol>
<controlAddress>
<!opt -->
<enabled>
<Address>
<!opt, xs:string 1-255 --> </Address>
</controlAddress><
<defaultPresetID>  </defaultPresetID>
<panSupport> <!ro,opt, xs:boolean --> </panSupport>
<tiltSupport> <!ro,opt, xs:boolean --> </tiltSupport>
<zoomSupport> <!ro,opt, xs:boolean --> </zoomSupport>
</PTZChannel>
8.13.3
/PTZCtrl/channels/<ID>/homeposition
/PTZCtrl/channels/<ID>/homeposition
PUT

Operator
Description
It is used to set the current horizontal position as horizontal

coordinate zero point for the device
Query
None
Inbound Data
None
Success Return
DELETE

111
Operator
Description
It is used to delete system horizontal coordinate zero point and

restore default zero point for the device (The photoelectric detection
location)
Query
None
Inbound Data
None
Success Return
Notes:
8.13.4
/PTZCtrl/channels/<ID>/homeposition/goto
/PTZCtrl/channels/<ID>/homeposition/goto
General Resource
v1.0
PUT
Operator
Description
It is used to move a particular PTZ channel to horizontal

coordinate zero point position for the device.
Query
None
Inbound Data
None
Success Return
Notes:
8.13.5
/PTZCtrl/channels/<ID>/continuous
/PTZCtrl/channels/<ID>/continuous
PUT

Operator
Description
It is used to control PTZ move around and zoom for the device.
Query
pan, tilt, zoom
Inbound Data
PTZData
Success Return
Notes:
PTZData XML Block

<PTZData version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<pan>  </pan>
<tilt>  </tilt>
<zoom>  </zoom>
</PTZData>

112
8.13.6
/PTZCtrl/channels/<ID>/momentary
/PTZCtrl/channels/<ID>/momentary
PUT
Operator
Description
It is used to control PTZ move around and zoom in a period of time

for the device.
Query
pan, tilt, zoom, duration
Inbound Data
PTZData
Success Return
Notes:
PTZData XML Block

<pan>  </pan>
<tilt>  </tilt>
<zoom>  </zoom>
<Momentary>
< duration> <!opt , xs:integer, milliseconds --> </duration>
</Momentary>
</PTZData>
8.13.7
/PTZCtrl/channels/<ID>/relative
/PTZCtrl/channels/<ID>/relative
PUT

Operator
Description
Pans, tilts, and/or zooms the device relative to the current position.
Query
positionX, positionY, relativeZoom
Inbound Data
PTZData
Success Return
Notes:
Mouse clicking function

PTZData XML Block
<Relative>
<positionX>  </positionX>
<positionY>  </positionY>
<relativeZoom>  </relativeZoom>
</Relative>
</PTZData>

113
8.13.8
/PTZCtrl/channels/<ID>/absolute
/PTZCtrl/channels/<ID>/absolute
PUT

Operator
Description
It is used to move a particular PTZ channel to a absolute position

which is defined by Absolute for the device.
Query
elevation, azimuth, absoluteZoom
Inbound Data
PTZData
Success Return
Notes:
Absolute position function

<AbsoluteHigh> is high precision positioning which is accurate to a bit after the decimal
point; For example elevation -900..2700 is corresponding to vertical -90.0-270.0 degree, and
azimuth 0..3600 is corresponding to horizontal 0.0-360.0 degree, absoluteZoom is corresponding
to zoom 0.0..100.0;
PTZData XML Block
<AbsoluteHigh>
<elevation>  </elevation>
<azimuth>  </azimuth>
<absoluteZoom>  </absoluteZoom>
</AbsoluteHigh>
</PTZData>
8.13.9
/PTZCtrl/channels/<ID>/digital
/PTZCtrl/channels/<ID>/digital
PUT

Operator
Description
It is used to move the position number which is defined by positionX,

position to the screen center and digital zoom for the device.
Query
position, positionY, digitalZoomLevel
Inbound Data
PTZData
Success Return
Notes:
Digital zoom function

digitalZoomLevel: 0 indicates that maintain the original image ratio.
PTZData XML Block
114

<Digital>
<positionX>  </positionX>
<positionY>  </positionY>
<digitalZoomLevel>  </digitalZoomLevel>
</Digital>
</PTZData>
8.13.10 /PTZCtrl/channels/<ID>/status
/PTZCtrl/channels/<ID>/status
GET
Viewer
Description
It is used to get currently PTZ coordinate position for the device.
Query
None
Inbound Data
None
Success Return
PTZStatus
Notes:
<AbsoluteHigh> is high precision positioning which is accurate to a bit after the decimal
point; For example elevation -900..2700 is corresponding to vertical -90.0-270.0 degree, and
azimuth 0..3600 is corresponding to horizontal 0.0-360.0 degree, absoluteZoom is corresponding
to zoom 0.0..100.0;
PTZStatus XML Block

< PTZStatus version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<AbsoluteHigh>
<elevation>  </elevation>
<azimuth>  </azimuth>
<absoluteZoom>  </absoluteZoom>
</AbsoluteHigh>
</PTZStatus>
8.13.11 /PTZCtrl/channels/<ID>/presets
/PTZCtrl/channels/<ID>/presets
GET

Viewer
Description
It is used to get preset configuration information of a particular PTZ

channel for the device.
Query
None

115
Inbound Data
None
Success Return
PTZPresetList
PUT
Operator
Description
It is used to update preset configuration information of a particular

PTZ channel for the device.
Query
None
Inbound Data
PTZPresetList
Success Return
POST
Operator
Description
It is used to add preset configuration information of a particular PTZ

Query
None
Inbound Data
PTZPreset
Success Return
DELETE
Administrator
Description
It is used to delete preset configuration information of a particular

Query
None
Inbound Data
None
Success Return
Notes:
PTZPresetList XML Block

<PTZPresetList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<PTZPreset> 
</PTZPresetList>
8.13.12 /PTZCtrl/channels/<ID>/presets/<ID>
/PTZCtrl/channels/<ID>/presets/<ID>
GET

Viewer
Description
It is used to get particular preset configuration information of a

particular PTZ channel for the device.
Query
None
Inbound Data
None
Success Return
PTZPreset
PUT
Description
Operator
It is used to update particular preset configuration information of a

116
Query
None
Inbound Data
PTZPreset
Success Return
DELETE
Operator
Description
It is used to delete particular preset configuration information of a

Query
None
Inbound Data
None
Success Return
Notes:
<id> indicates the preset number.

<presetName> indicates the preset name
Enable is used to indicate whether preset have been set.
PUT is used to set preset and update title of new preset. (Enable value import to
PTZPreset should be 1 when PUT )
PTZPreset XML Block
<PTZPreset version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>  </id>
<presetName>  </presetName>
</PTZPreset>
8.13.13 /PTZCtrl/channels/<ID>/presets/<ID>/goto
/PTZCtrl/channels/<ID>/presets/<ID>/goto
PUT
Operator
Description
It is used to move a particular PTZ channel to a ID preset position for

the device.
Query
None
Inbound Data
None
Success Return
Notes:
8.13.14 /PTZCtrl/channels/<ID>/patrols
/PTZCtrl/channels/<ID>/patrols
GET
Description

Viewer
It is used to get patrol configuration information of a particular PTZ

117

Query
None
Inbound Data
None
Success Return
PTZPatrolList
PUT
Operator
Description
It is used to update patrol configuration information of a particular

Query
None
Inbound Data
PTZPatrolList
Success Return
POST
Operator
Description
It is used to add a patrol point configuration for a particular PTZ

channel.
Query
None
Inbound Data
PTZPatrol
Success Return
DELETE
Administrator
Description
It is used to delete patrol configuration for a particular PTZ channel.
Query
None
Inbound Data
None
Success Return
Notes: It is similar with preset.
PTZPatrolList XML Block

<PTZPatrolList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<PTZPatrol> 
</PTZPatrolList>
8.13.15 /PTZCtrl/channels/<ID>/patrols/<ID>
/PTZCtrl/channels/<ID>/patrols/<ID>
GET

Viewer
Description
It is used to get a particular patrol route configuration of a particular

PTZ channel.
Query
None
Inbound Data
None
Success Return
PTZPatrol
PUT
Description
Operator
It is used to update a particular patrol configuration of a particular
PTZ channel.

118
Query
None
Inbound Data
PTZPatrol
Success Return
DELETE
Operator
Description
It is used to delete a particular patrol route configuration of a

particular PTZ channel
Query
None
Inbound Data
None
Success Return
Notes:
<PatrolSequence> indicates the patrol point.

< presetID > indicates the preset number
<seqSpeed> indicates the patrol speed
<delay> indicates the dwell time, in seconds
PTZPatrol XML Block
<patrolName>  </patrolName>
<resumeType>  </resumeType>
<PatrolSequenceList> 
<PatrolSequence> 
<id> </id>
<presetID>  </presetID>
<seqSpeed>  </seqSpeed>
<delay>  </delay>

</PatrolSequence>
</PatrolSequenceList>
</PTZPatrol>
8.13.16 /PTZCtrl/channels/<ID>/patrols/<ID>/start
/PTZCtrl/channels/<ID>/patrols/<ID>/start
PUT

Operator
Description
It is used to start running particular patrol route of a particular PTZ

channel.
Query
None
Inbound Data
None
Success Return
Notes:

119
8.13.17 /PTZCtrl/channels/<ID>/patrols/<ID>/stop
/PTZCtrl/channels/<ID>/patrols/<ID>/stop
PUT
Operator
Description
It is used to stop running particular patrol route of a particular PTZ

channel.
Query
None
Inbound Data
None
Success Return
Notes:
It is available to stop the patrol route which is in running state or in pause state.
8.13.18 /PTZCtrl/channels/<ID>/patrols/<ID>/pause
/PTZCtrl/channels/<ID>/patrols/<ID>/pause
PUT

Operator
Description
It is used to pause particular patrol route which is in running state of a

particular channel.
Query
None
Inbound Data
None
Success Return
Notes:
Patrolstart is used to restart patrol route.

It doesnt support dome at this moment.
8.13.19 /PTZCtrl/channels/<ID>/patrols/<ID>/status
/PTZCtrl/channels/<ID>/patrols/<ID>/status
GET
Viewer
Description
It is used to get particular patrol route state of a particular PTZ

channel.
Query
None
Inbound Data
PTZPatrolStatus
Success Return
Notes:
It doesnt support dome at this moment!!

PTZPatrolStatus XML Block
120
<PTZPatrolStatus> <!opt -->

<patrolID>  </patrolID>
<patrolStatus>  </patrolStatus>
</PTZPatrolStatus>
</PTZPatrol>
8.13.20 /PTZCtrl/channels/<ID>/patrols/<ID>/schedule
/PTZCtrl/channels/<ID>/patrols/<ID>/schedule
GET
Viewer
Description
It is used to get patrol schedule of a particular PTZ channel.
Query
None
Inbound Data
None
Success Return
TimeBlockList
PUT
Operator
Description
It is used to update patrol schedule of a particular PTZ channel.
Query
None
Inbound Data
TimeBlockList
Success Return
Notes:
8.13.21 /PTZCtrl/channels/<ID>/patterns
/PTZCtrl/channels/<ID>/patterns
GET

Viewer
Description
It is used to get pattern configuration of a particular PTZ channel.
Query
None
Inbound Data
None
Success Return
PTZPatternList
Notes:
It is similar to presets!!
DELETE
Operator
Description
It is used to delete all patterns configuration of a particular PTZ

channel
Query
None
Inbound Data
None
Success Return
PTZPatternList XML Block

<PTZPatternList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
121
<PTZPattern> 

</ PTZPatternList >
8.13.22 /PTZCtrl/channels/<ID>/patterns/<ID>
/PTZCtrl/channels/<ID>/patterns/<ID>
GET

Viewer
Description
It is used to get a particular pattern configuration of a particular PTZ

channel.
Query
None
Inbound Data
None
Success Return
PTZPattern
PUT
Operator
Description
It is used to update a particular pattern configuration of a particular

PTZ channel.
Query
None
Inbound Data
PTZPattern
Success Return
DELETE
Operator
Description
It is used to delete a particular pattern configuration of a particular

PTZ channel
Query
None
Inbound Data
None
Success Return
Notes:
<space> x% indicates the remaining space for pattern

PTZPattern XML Block
<PTZPattern version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<space> 
</space>
</PTZPattern>

122
8.13.23 /PTZCtrl/channels/<ID>/patterns/<ID>/recordst
art
/PTZCtrl/channels/<ID>/patterns/<ID>/recordstart
PUT

Operator
Description
It is used to start particular pattern information recording of a

particular PTZ channel.
Query
None
Inbound Data
None
Success Return
Notes:
Remaining space information will be uploaded in real time during the recording process.
8.13.24 /PTZCtrl/channels/<ID>/patterns/<ID>/recordst
op
/PTZCtrl/channels/<ID>/patterns/<ID>/recordstop
PUT

Operator
Description
It is used to stop a particular pattern information recording of a

particular PTZ channel
Query
None
Inbound Data
None
Success Return
Notes:
8.13.25 /PTZCtrl/channels/<ID>/patterns/<ID>/run
/PTZCtrl/channels/<ID>/patterns/<ID>/run
PUT

Operator
Description
It is used to start a particular pattern of a particular PTZ channel.
Query
None
Inbound Data
None
Success Return
Notes:

123
8.13.26 /PTZCtrl/channels/<ID>/patterns/<ID>/stop
/PTZCtrl/channels/<ID>/patterns/<ID>/stop
PUT
Operator
Description
It is used to stop a particular pattern which is in running status of a

particular PTZ channel.
Query
None
Inbound Data
None
Success Return
Notes:
8.13.27 /PTZCtrl/channels/<ID>/PTZOSDDisplay
/PTZCtrl/channels/<ID>/PTZOSDDisplay
GET

Viewer
Description
It is used to get OSD display information of a particular PTZ channel.
Query
None
Inbound Data
None
Success Return
PTZOSDDisplay
PUT
Operator
Description
It is used to update OSD display information of a particular PTZ

channel.
Query
None
Inbound Data
PTZOSDDisplay
Success Return
Notes:
<zoomlable> indicates the zoom progress bar display

<azimuth> indicates the azimuth display
<presetlable> indicates the preset title display
PTZOSDDisplay XML Block
<PTZOSDDisplay version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<zoomlable>

</zoomlable>
<azimuth>
</azimuth>
<presetlable>
124
</presetlable>
</PTZOSDDisplay>
8.13.28 /PTZCtrl/channels/<ID>/parkaction
/PTZCtrl/channels/<ID>/parkaction
GET
Viewer
Description
It is used to get park action information of a PTZ channel.
Query
None
Inbound Data
None
Success Return
ParkAction
PUT
Operator
Description
It is used to update park action information of a PTZ channel.
Query
None
Inbound Data
ParkAction
Success Return
Notes:
<Parktime> Time span that will trigger an park action

<Action> park action
<ActionNum> park action number. It is used when park action is patrol, pattern or preset.
For others, it is 0
ParkAction XML Block
<ParkAction version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<Parktime>  </Parktime>
<Action>
<ActionType>

</ActionType>
<ActionNum>
</Action>
</ParkAction>

</ActionNum>
8.13.29 /PTZCtrl/channels/<ID>/ptzlimiteds
/PTZCtrl/channels/<ID>/ptzlimiteds
GET
Description
Viewer
It is used to get movement limitations of PTZ channels.

125
Query
None
Inbound Data
None
Success Return
PTZLimitedList
Notes:
PUT
Viewer
Description
It is used to set movement limitations of PTZ channels.
Query
None
Inbound Data
None
Success Return
PTZLimitedList
Notes:
DELETE
Description
It is used to clear movement limitations of a PTZ channel.
Query
None
Inbound Data
None
Success Return
PTZLimitedList XML Block

<PTZLimitedList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled></enabled>
<PTZLimited> 
</ PTZLimitedList>
8.13.30 /PTZCtrl/channels/<ID>/ptzlimiteds/<ID>
/PTZCtrl/channels/<ID>/ptzlimiteds/<ID>
GET
Viewer
Description
It is used to get movement limitations of a PTZ channel.
Query
None
Inbound Data
None
Success Return
PTZLimited
DELETE
Description
It is used to clear movement limitations of a PTZ channel.
Query
None
Inbound Data
None
Success Return
Notes:
It is used to get or set the parameter that whether movement limitation is enabled or
disabled.
Speed dome add two types of movement limitation.

126
<ID>=1 Manual control movement limitation <ID>=2 Panorama scan movement limitation
PTZLimited XML Block
<PTZLimited version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
</PTZLimited>
8.13.31 /PTZCtrl/channels/<ID>/ptzlimiteds/<ID>/setsta
rt
/PTZCtrl/channels/<ID>/ptzlimiteds/<ID>/setstart
General Resource
v1.0
PUT
Operator
Description
Set the start position of a movement limitation of a PTZ

channel.
Query
None
Inbound Data
None
Success Return
Notes:
Only used when movement limitation is enabled.
8.13.32 /PTZCtrl/channels/<ID>/ptzlimiteds/<ID>/set
/PTZCtrl/channels/<ID>/ptzlimiteds/<ID>/set
PUT
General Resource
v1.0
Operator
Description
Set other positions of a movement limitation of a PTZ channel.
Query
None
Inbound Data
None
Success Return
Notes:
Only used when movement limitation is enabled and setstart already been used.
Order of the positions is leftrightupdown. Please save the settings after setup.
8.13.33 /PTZCtrl/channels/<ID>/saveptzpoweroff
/PTZCtrl/channels/<ID>/saveptzpoweroff
GET

127

Viewer
Description
It is used to get the PTZ power off memory settings information
Query
None
Inbound Data
None
Success Return
PTZChannel
PUT
Operator
Description
It is used to update the PTZ power off memory settings information
Query
None
Inbound Data
PTZChannel
Success Return
Notes:
<savePtzPoweroff>Power off memory

savePtzPoweroff XML Block
<savePtzPoweroff version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<savePtzPoweroffType>

</savePtzPoweroffType>
</savePtzPoweroff>
8.13.34 /PTZCtrl/channels/<ID>/timetasks
/PTZCtrl/channels/<ID>/timetasks
GET
Viewer
Description
It is used to get a list of tasks based on a schedule
Query
None
Inbound Data
None
Success Return
TimeTaskList
PUT
Operator
Description
It is used to update a list of tasks based on a schedule
Query
None
Inbound Data
TimeTaskList
Success Return
Notes:
GET is used to get a list of tasks of a whole week(7)

<enabled>Enable all the tasks
<Parktime> Time span for a task to resume.
DELETE
Operator
Description
It is used to delete all lists of tasks
Query
None

128
Inbound Data
None
Success Return
TimeTaskList XML Block

<TimeTaskList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<Parktime>  </Parktime>
<TimeTaskBlock /> 
</TimeTaskList>
8.13.35 /PTZCtrl/channels/<ID>/timetasks/<ID>
/PTZCtrl/channels/<ID>/timetasks/<ID>
GET
Viewer
Description
It is used to get a list of tasks of one day
Query
None
Inbound Data
None
Success Return
TimeTaskBlock
PUT
Operator
Description
It is used to update a list of tasks of one day
Query
None
Inbound Data
TimeTaskBlock
Success Return
DELETE
Operator
Description
It is used to delete a list of tasks of one day
Query
None
Inbound Data
None
Success Return
Notes:
Tasks based on a schedule consist of time blocks ad tasked. This task is enabled always.
<TimeTaskBlock> get all the time span and tasks of one day
<dayOfWeek> specify the day of a week, ranging from 1 to 7
<TimeTaskRange> time span of each task. Up to ten time spans and 10 tasks are
supported in one day.
<beginDateTime> specify the begin time of each task, ranig from 0:0:0-23:59:00, format is
consistent to ISO 8601.
<endDateTime> specify the end time of each task, ranig from 0:0:0-23:59:00, format is
consistent to ISO 8601. endDateTime should be larger than or equal to beginDateTime.
<TaskType> Tasks type
<TaskNum> Tasks number. Enabled when park action is patrol, pattern, preset or
auxoutput, otherwise the value is 0.
129
TimeTaskBlock XML Block

<TimeTaskBlock version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<dayOfWeek>

</dayOfWeek>
<TimeTaskRange>
<TaskID></TaskID>
<Task>
<TaskType>

</TaskType>
<TaskNum></TaskNum>
</Task>
</TimeTaskRange>
</TimeTaskBlock>
8.13.36 /PTZCtrl/channels/<ID>/timetasks
/<ID>/copytask
/PTZCtrl/channels/<ID>/timetasks/<ID>/copytask
GET

Viewer
Description
It is used to get the default copy time of a tasks list of a specified PTZ
channel.
Query
None
Inbound Data
None
Success Return
TimeTaskCopy
PUT
Operator
Description
It is used to update the default copy time of a tasks list of a specified

PTZ channel.
Query
None
Inbound Data
TimeTaskCopy
Success Return
Notes:
<curDayOfWeek> specify the current day of a week

<copyDayOfWeek> specify the days that will have the same settings as the current day

130
TimeTaskCopy XML Block

<TimeTaskCopy version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<curDayOfWeek>
</curDay>
<copyDayOfWeek>
</copyDay>
</TimeTaskCopy >
8.13.37 /PTZCtrl/channels/<ID>/auxcontrol
/PTZCtrl/channels/<ID>/auxcontrol
GET
Description

Viewer
It is used to get auxillary PTZ control information of a specified

PTZchannel.
Query
command
Inbound Data
None
Success Return
PTZAuxStatus
PUT
Operator
Description
It is used to update auxillary PTZ control information of a specified

PTZchannel.
Query
command
Inbound Data
PTZAuxStatus
Success Return
Notes:
Auxillary PTZ functions:

Commands:
LIGHT_PWRON: open light
WIPER_PWRON: turn on wiper
FAN_PWRON: turn on fun
HEATER_PWRON: turn on heater
<enabled> 1 means turned on, 0 means turned off.
PTZAuxStatus XML Block
<PTZAuxStatus version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
</PTZAuxStatus>

131
8.13.38 /PTZCtrl/channels/<ID>/onepushfoucs/start
/PTZCtrl/channels/<ID>/onepushfoucs/start
PUT
Operator
Description
It is used to start focusing by pushing a key.
Query
None
Inbound Data
None
Success Return
Notes:
8.13.39 /PTZCtrl/channels/<ID>/onepushfoucs/reset
/PTZCtrl/channels/<ID>/onepushfoucs/reset
PUT
Operator
Description
IPC Lens initialization
Query
None
Inbound Data
None
Success Return
Notes:
8.13.40 /PTZCtrl/channels/<ID>/position3D
/PTZCtrl/channels/<ID>/position3D
PUT
Operator
Description
It is used to set 3D zoom of a particular PTZ channel.
Query
None
Inbound Data
Position3D
Success Return
Notes:
Position3D XML Block

<Position3D version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<StartPoint>
<positionX>  </positionX>
<positionY>  </positionY>
</StartPoint>

132
<EndPoint>
<positionX>  </positionX>
<positionY>  </positionY>
</EndPoint>
</Position3D>
8.14 Image
/Image
Service v1.0
Notes: service of camera Image
8.14.1
/Image/channels
/Image/channels
GET
Viewer
Description
It is used to get the list of channel Image configuration.
Query
None
Inbound Data
None
Success Return
ImageChannellist
PUT
Operator
Description
It is used to update Image configuration for all channels.
Query
None
Inbound Data
ImageChannellist
Success Return
Notes:
ImageChannellist XML Block

<ImageChannellist version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<ImageChannel/> 
</ImageChannellist>
8.14.2
/Image/channels/<ID>
GET
Viewer
Description
It is used to get a special channel Image configuration.
Query
None

133
Inbound Data
None
Success Return
ImageChannel
PUT
Operator
Description
It is used to update Image configuration for a special channel.
Query
None
Inbound Data
ImageChannel
Success Return
Notes:
ImageChannellist XML Block

<ImageChannel version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id></id>
<videoInputID>
<resetImage/>
<restoreImageparam/> 
<Focus/> 
<LensInitialization /> 
<ImageFilp/> 
<ImageFreeze/> 
<proportionalpan/> 
<WDR/> 
<BLC/> 
<NoiseReduce/> 
<ImageEnhancement/> 
<IrcutFilter/> 
<DSS/> 
<WhiteBlance/> 
<Exposure/> 
<Sharpness/> 
<Iris/> 
<Shutter/> 
<Gain/> 
<gamaCorrection/> 
<powerLineFrequency/> 
<Color/> 
<NosiseReduceExt/> 
<IrcutFilterExt/> 
<WDRExt/> 
<Scene/> 
< EPTZ/ > 
< PTZ/> 
134
<EIS/> 

<HLC/> 
<ChromaSuppress/> 
<ZoomLimit/> 
<ExpComp/> 
</ImageChannel>
8.14.3
/Image/channels/<ID>/resetImage
/Image/channels/<ID>/resetImage
PUT

Operator
Description
It is used to reset an image channel (cut off the power and reboot the
speed dome).
Query
None
Inbound Data
None
Success Return
Notes: Image reset only reboot the camera unit.
8.14.4
/Image/channels/<ID>/restoreImageparam
/Image/channels/<ID>/restoreImageparam
PUT

Operator
Description
It is used to reset the image configure parameter to the factory

default.
Query
None
Inbound Data
None
Success Return
Notes:
8.14.5
/Image/channels/<ID>/Focus
/Image/channels/<ID>/Focus
GET

Viewer
Description
It is used to get focus parameters of a specified image channel.
Query
None

135
Inbound Data
None
Success Return
Focus
PUT
Operator
Description
It is used to update focus parameters of a specified image channel.
Query
None
Inbound Data
Focus
Success Return
Notes:
AUTO: auto focus

MANUAL: manual focus
SEMIAUTOMATIC: semi automatic
FocusValues PUT operator is enabled only when FocusStyles value is MANUAL.
focusSpeed: focus vector data. Negative numbers focus near, positive numbers focus far.
Numerical value is a percentage of the maximum focus speed of the lens module.
Focus XML Block
<Focus version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<FocusStyle/> 
<FocusLimited/> 
<FocusValue/> 
<focusSpeed>  </focusSpeed>
</Focus>
8.14.6
/Image/channels/<ID>/LensInitialization
/Image/channels/<ID>/ LensInitialization
GET

Viewer
Description
It is used to get the initizlization status of the lens of a specified image

channel.
Query
None
Inbound Data
None
Success Return
LensInitialization
PUT
Operator
Description
It is used to update focus parameters of a specified image channel.
Query
None
Inbound Data
LensInitialization
Success Return
Notes:
136
LensInitialization XML Block

<LensInitialization version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled/>
</LensInitialization>
8.14.7
/Image/channels/<ID>/ImageFlip
/Image/channels/<ID>/ImageFlip
GET
Viewer
Description
It is used to get the mirror status of a specified image channel.
Query
None
Inbound Data
None
Success Return
ImageFlip
PUT
Operator
Description
It is used to update mirror status of a specified image channel.
Query
None
Inbound Data
ImageFlip
Success Return
ResponseStaus ResponseStatus
Notes:
ImageFlipStyle is enabled only when enabled value is true.

ImageFlip XML Block
<ImageFlip version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled/>

<ImageFlipStyle/> 
</ImageFlip>
8.14.8
/Image/channels/<ID>/ImageFreeze
/Image/channels/<ID>/ImageFreeze
GET

Viewer
Description
It is used to get ImageFreeze status of a specified Image channel.
Query
None
Inbound Data
None
Success Return
ImageFreeze
PUT
137
Operator
Description
It is used to update ImageFreeze status of a specified image

channel.
Query
None
Inbound Data
ImageFreeze
Success Return
Notes:
ImageFreeze XML Block

<ImageFreeze version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled/>
</ImageFreeze>
8.14.9
/Image/channels/<ID>/proportionalpan
/Image/channels/<ID>/proportionalpan
GET
Viewer
Description
It is used to get
channel.
Query
None
Inbound Data
None
Success Return
proportionalpan
proportional pan status of a specified image
PUT
Operator
Description
It is used to update proportional pan status of a specified image

channel.
Query
None
Inbound Data
proportionalpan
Success Return
Notes:
proportionalpan XML Block

<proportionalpan version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled/> 
</proportionalpan >
8.14.10 /Image/channels/<ID>/WDRExt
/Image/channels/<ID>/WDRExt
GET
138
General Resource v1.5.9

Viewer
Description
It is used to get the value of wide dynamic range for a specified

Image channel.
Query
None
Inbound Data
None
Success Return
WDRExt
PUT
Operator
Description
It is used to configure the value of wide dynamic range for a specified

Image channel.
Query
None
Inbound Data
WDRExt
Success Return
Notes:
<WDRLevelExt> is optional; some cameras may use more than one level to control WDR
working.
<mode> value can be open,close or auto , some cameras may not surpport the auto
mode . If a camera works in auto mode, WDR would automatically open or close
according to scene.
WDRExt XML Block
<WDRExt version=1.5.9 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<mode>
 </mode>
<WDRLevel> </WDRLevel>
<WDRContrastLevel>  </WDRContrastLevel>
<WDRLevelExt> 
<Level2>  < /Level2>
</WDRLevelExt>
</WDRExt >
8.14.11 /Image/channels/<ID>/BLC
/Image/channels/<ID>/BLC
GET

Viewer
Description
It is used to get the configuration of backlight compensation for a

specified image channel.
Query
None
Inbound Data
None
Success Return
BLC
PUT
Description
Operator
It is used to configure the configuration of backlight compensation for
a specified image channel.

139
Query
None
Inbound Data
BLC
Success Return
Notes:
BLC XML Block

<BLC version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled/>
<BLCMode/>

<BLCRegionList>
<BLCRegion>
<id> </id>
<RegionCoordinatesList/>
</BLCRegion>
<BLCRegionList>
</BLC>
CENTER,
8.14.12 /Image/channels/<ID>/Imageenhancement
/Image/channels/<ID>/Imageenhancement
GET

Viewer
Description
It is used to get the ImageEnhancement's configuration of a specified

image channel.
Query
None
Inbound Data
None
Success Return
ImageEnhancement
PUT
Operator
Description
It is used to configure the ImageEnhancement's configuration of a

Query
None
Inbound Data
ImageEnhancement
Success Return
Notes:
Imageenhancement XML Block

<ImageEnhancement version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled/> 
<ImageEnhancementLevel> 
</ImageEnhancement>
140
8.14.13 /Image/channels/<ID>/IrcutFilterExt
/Image/channels/<ID>/IrcutFilterExt
GET

Viewer
Description
It is used to get the IrcutFilter's configuration of a specified image

channel.
Query
None
Inbound Data
None
Success Return
IrcutFilterExt
PUT
Operator
Description
It is used to configure the IrcutFilter's configuration of a specified

image channel.
Query
None
Inbound Data
IrcutFilterExt
Success Return
Notes:
IrcutFilter XML Block

<IrcutFilterExt version=1.5.9 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<IrcutFilterType>

</IrcutFilterType>
<dayToNightFilterLevel></dayToNightFilterLevel>
<dayToNightFilterTime>  </dayToNightFilterTime>
<nightToDayFilterLevel></nightToDayFilterLevel>
<nightToDayFilterTime> </nightToDayFilterTime>
<Schedule> 
<scheduleType><!req,xs:string,day,night></scheduleType>
<TimeRange> 
</TimeRange>
</Schedule>
<EventTrigger> 
<eventType></mode>
<GeneralMode> 
<generalLevel></generalLevel>
</GeneralMode>
<AdvancedMode>
<FrameNoiseReduceLevel></FrameNoiseReduceLevel>
<InterFrameNoiseReduceLevel></InterFrameNoiseReduc
eLevel>
</AdvancedMode>
</NoiseReduceExt>

142
8.14.15 /Image/channels/<ID>/DSS
/Image/channels/<ID>/DSS
GET
Viewer
Description
It is used to get the the configuration of digital slow shutter for a

specified Image channel.
Query
None
Inbound Data
None
Success Return
DSS
PUT
Operator
Description
It is used to configure the configuration of digital slow shutter for a

Query
None
Inbound Data
DSS
Success Return
Notes: DSSLevel is only enabled when enabled value is true.
DSS XML Block

<DSS version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled/>
<DSSLevel/> <!opt, xs:string, low, normal, high -->
</DSS>
8.14.16 /Image/channels/<ID>/WhiteBlance
/Image/channels/<ID>/WhiteBlance
GET

Viewer
Description
It is used to get the WhiteBlance value of a specified iImage channel.
Query
None
Inbound Data
None
Success Return
WhiteBlance
PUT
Operator
Description
It is used to configure the WhiteBlance value of a specified iImage

channel.
Query
None
Inbound Data
WhiteBlance
Success Return
Notes: WhiteBlanceRed and WhiteBlanceBlues PUT operator is enabled only when
WhiteBlanceStyles value is manual.

143
WhiteBlance XML Block

<WhiteBlance version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<WhiteBlanceStyle/> 
<WhiteBlanceRed/> 
<WhiteBlanceBlue/> 
</WhiteBlance>
8.14.17 /Image/channels/<ID>/Exposure
/Image/channels/<ID>/Exposure
GET
Viewer
Description
It is used to get the exposure mode of a specified image channel.
Query
None
Inbound Data
None
Success Return
Exposure
PUT
Operator
Description
It is used to configure the exposure mode of a specified image

channel.
Query
None
Inbound Data
Exposure
Success Return
Notes:
hik:Exposure XML Block

<Exposure version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<ExposureType/> 
<OverexposeSuppress> 
<enabled>  </enabled>
<OverexposeSuppress>
</Exposure>
8.14.18 /Image/channels/<ID>/Sharpness
/Image/channels/<ID>/Sharpness
GET
Description

Viewer
It is used to get the sharpness's value of a specified image channel.

144
Query
None
Inbound Data
None
Success Return
Sharpness
PUT
Operator
Description
It is used to configure the sharpness's value of a specified image

channel.
Query
None
Inbound Data
Sharpness
Success Return
Notes:
Sharpness XML Block

<Sharpness version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<SharpnessLevel/> 
<SharpnessMode></ SharpnessMode >
</Sharpness>
8.14.19 /Image/channels/<ID>/Iris
/Image/channels/<ID>/Iris
GET
Viewer
Description
It is used to get the iris's value of a specified image channel.
Query
None
Inbound Data
None
Success Return
Iris
PUT
Operator
Description
It is used to configure the iris's value of a specified image channel.
Query
None
Inbound Data
Iris
Success Return
Notes: Iriss PUT operate is enabled only when <ExposureType> is IrisFirst
irisSpeed: negative numbers close iris, positive numbers open iris. Numerical value is a
percentage of the maximum iris speed of the lens module.
hik:IrisValue XML Block
<Iris version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<IrisLevel/>

<irisSpeed>

</irisSpeed>
145
</Iris>
8.14.20 /Image/channels/<ID>/Shutter
/Image/channels/<ID>/Shutter
GET

Viewer
Description
It is used to get the Shutter value of a specified image channel.
Query
None
Inbound Data
None
Success Return
Shutter
PUT
Operator
Description
It is used to configure the Shutter value of a specified image channel.
Query
None
Inbound Data
Shutter
Success Return
Notes: Shutter's PUT operate is enabled only when <ExposureType> is ShutterFirst
hik:ShutterValue XML Block

<Shutter version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<ShutterLevel/>

</Shutter>
8.14.21 /Image/channeles/<ID>/Gain
/Image/channels/<ID>/Gain
GET

Viewer
Description
It is used to get the gain configuration of a specified Image channel.
Query
None
Inbound Data
None
Success Return
Gain
PUT
Operator
Description
It is used to configure the gain configuration of a specified Image

channel.
Query
None

146
Inbound Data
Gain
Success Return
Notes: Gains PUT operate is enabled only when <ExposureType> is gainFirst.
hik:gain XML Block

<Gain version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<GainLevel/> 
<GainWindow>
<RegionCoordinatesList> 
<RegionCoordinates>
<positionX></positionX>
<positionY></positionY>
</GainWindow>
</Gain>
8.14.22 /Image/channeles/<ID>/GamaCorrection
/Image/channels/<ID>/gamaCorrection
GET

Viewer
Description
It is used to get the gama correction of a specified Image channel.
Query
None
Inbound Data
None
Success Return
gammaCorrection
PUT
Operator
Description
It is used to configure the gama correction of a specified Image

channel.
Query
None
Inbound Data
gammaCorrection
Success Return
Notes:
hik:gammaCorrection XML Block

<gammaCorrection version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<gammaCorrectionEnabled>  </gammaCorrectionEnabled>
<gammaCorrectionLevel>  </gammaCorrectionLevel>
</gammaCorrection>

147
8.14.23 /Image/channels/<ID>/powerLineFrequency
/Image/channels/<ID>/powerLineFrequency
GET
Viewer
Description
It is used to get the powerLineFrequency value of a specified Image

channel.
Query
None
Inbound Data
None
Success Return
powerLineFrequency
PUT
Operator
Description
It is used to configure the powerLineFrequency value of a specified

Image channel.
Query
None
Inbound Data
powerLineFrequency
Success Return
Notes: Configure the powerlineFrequency requires to reboot the camera.
hik:powerlineFrequency XML Block

<powerLineFrequency version=1.0 mlns=http://www.hikvision.com/ver10/XMLSchema>
<powerLineFrequencyMode> 
</powerLineFrequencyMode>
</powerLineFrequency >
8.14.24 /Image/channels/<ID>/Color
/Image/channels/<ID>/Color
GET

Viewer
Description
It is used to get the color's value of a specified Image channel.
Query
None
Inbound Data
None
Success Return
Color
PUT
Operator
Description
It is used to configure the color's value of a specified Image channel.
Query
None
Inbound Data
Color
Success Return
Notes:

148
Color XML Block

<Color version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<brightnessLevel>

</brightnessLevel>
<contrastLevel>

</contrastLevel>
<saturationLevel>

</saturationLevel>
<hueLevel>
</ hueLevel >
<grayScale>
<grayScaleMode> <grayScaleMode>
<grayScale>
</Color>
8.14.25 /Image/channels/<ID>/Scene
/Image/channels/<ID>/Scene
GET
Viewer
Description
It is used to get sene mode of a camera.
Query
None
Inbound Data
None
Success Return
Scene
PUT
Operator
Description
It is used to set sene mode of a camera.
Query
None
Inbound Data
Scene
Success Return
Notes:
Scene XML Block

<Scene>
<mode></mode>
</Scene>
8.14.26 /Image/channels/<ID>/EPTZ
/Image/channels/<ID>/EPTZ
GET
Viewer
Description
It is used to get electronic PTZ enabled status.
Query
None

149
Inbound Data
None
Success Return
EPTZ
PUT
Operator
Description
It is used to get electronic PTZ enabled status.
Query
None
Inbound Data
EPTZ
Success Return
Notes:
EPTZ XML Block

< EPTZ>
<enabled></enabled >
< /EPTZ>
8.14.27 /Image/channels/<ID>/PTZ
/Image/channels/<ID>/PTZ
GET
Viewer
Description
It is used to get PTZ status. if a camera support PTZ, enabled tag

value is true , otherwise is false
Query
None
Inbound Data
None
Success Return
PTZ
PTZ XML Block

< PTZ>
<enabled></enabled >
< /PTZ >
8.14.28 /Image/channels/<ID>/EIS
/Image/channels/<ID>/EIS
GET
General Resource
v1.0
Viewer
Description
It is used to get the electronic-image-stabilizer configuration of a

Query
None
Inbound Data
None

150
Success Return
EIS
PUT
Operator
Description
It is used to set the the electronic-image-stabilizer configuration of a

Query
None
Inbound Data
EIS
Success Return
Notes:
EIS XML Block

<EIS version=1.5.9 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<EISLevel>  </EISLevel>
</EIS>
8.14.29 /Image/channels/<ID>/HLC
/Image/channels/<ID>/HLC
GET
Viewer
Description
It is used to get the high-light-compensation configuration of a

Query
None
Inbound Data
None
Success Return
HLC
PUT
Operator
Description
It is used to set the high-light-compensation configuration of a

specified image channe.
Query
None
Inbound Data
HLC
Success Return
Notes:
HLC XML Block

<HLC version=1.5.9 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<HLCLevel>  </HLCLevel>
</HLC>

151
8.14.30 /Image/channels/<ID>/ChromaSuppress
/Image/channels/<ID>/ChromaSuppress
GET
Viewer
Description
It is used to get the chroma-suppress configuration of a specified

image channel.
Query
None
Inbound Data
None
Success Return
ChromaSuppress
PUT
Operator
Description
It is used to set the chroma-suppress configuration of a specified

image channel.
Query
None
Inbound Data
ChromaSuppress
Success Return
Notes:
ChromaSuppress XML Block

<ChromaSuppress version=1.5.9 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<ChromaSuppressLevel>  </ChromaSuppressLevel>
</ChromaSuppress>
8.14.31 /Image/channels/<ID>/ZoomLimit
/Image/channels/<ID>/ZoomLimit
GET
Viewer
Description
It is used to get the zoomlimitconfiguration of a specified Image

channel.
Query
None
Inbound Data
None
Success Return
ZoomLimit
PUT
Operator
Description
It is used to set the zoomlimit value of the camera
Query
None
Inbound Data
ZoomLimit
Success Return
Notes:
152
ZoomLimit XML Block

<ZoomLimit version=1.5.9 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<ZoomLimitRatio> <!opt xs:integer --> </ZoomLimitRatio>
</ZoomLimit >
8.14.32 /Image/channels/<ID>/ExpComp
/Image/channels/<ID>/ExpComp
GET

Viewer
Description
It is used to get the value of exposure compensation for a specified

Image channel.
Query
None
Inbound Data
None
Success Return
ExpComp
PUT
Operator
Description
It is used to configure the value of exposure compensation for a

Query
None
Inbound Data
ExpComp
Success Return
Notes:
ExpComp XML Block

<ExpComp version=1.5.9 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled/>

<ExpCompLevel/> 
</ExpComp>
8.14.33 /Image/channels/<ID>/IrLight
/Image/channels/<ID>/IrLight
GET

Viewer
Description
It is used to get the IR Light configuration for a specified Image

channel.
Query
None
Inbound Data
None

153
Success Return
IrLight
PUT
Operator
Description
It is used to configure IR Light for a specified Image channel.
Query
None
Inbound Data
IrLight
Success Return
Notes:
IrLight XML Block

<IrLight version=1.5.9 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<mode>
 </mode>
<brightnessLevel>  </brightnessLevel>
<sensitivityLevel> <sensitivityLevel>
</IrLight >
8.14.34 /Image/channels/<ID>/WDR(1.5.8 old version)

/Image/channels/<ID>/WDR
GET
Viewer
Description
It is used to get the value of wide dynamic range for a specified

Image channel.
Query
None
Inbound Data
None
Success Return
WDR
PUT
Operator
Description
It is used to configure the value of wide dynamic range for a specified

Image channel.
Query
None
Inbound Data
WDR
Success Return
Notes:
The range of WDRLevel's value is needed according to the capbilites of devices.

WDR XML Block
<WDR version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled/>
<WDRLevel/>
<WDRContrastLevel/> 
</WDR>

154
8.14.35 /Image/channels/<ID>/NoiseReduce(1.5.8
old
version)
/Image/channels/<ID>/NoiseReduce
GET
Viewer
Description
It is used to get the NoiseReduce's value of a specified image

channel.
Query
None
Inbound Data
None
Success Return
NoiseReduce
PUT
Operator
Description
It is used to configure the NoiseReduce's value of a specified image

channel.
Query
None
Inbound Data
NoiseReduce
Success Return
Notes:
NoiseReduce XML Block

<NoiseReduce version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enabled/>
<NoiseReduceLevel> <!opt, xs:string, low, normal, high -->
</NoiseReduce>
8.14.36 /Image/channels/<ID>/IrcutFilter(1.5.8
old
version)
/Image/channels/<ID>/IrcutFilter
GET

Viewer
Description
It is used to get the IrcutFilter's configuration of a specified image

channel.
Query
None
Inbound Data
None
Success Return
IrcutFilter
PUT
Description
Operator
It is used to configure the IrcutFilter's configuration of a specified
image channel.

155
Query
None
Inbound Data
IrcutFilter
Success Return
Notes:
IrcutFilter XML Block

<IrcutFilter version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<IrcutFilterType/> 
<IrcutFilterLevel/> <!opt, xs:string, low, normal, high -->
<IrcutFilterTime/>
<!opt xs:integer -->
</IrcutFilter>
8.15 Record
/Record
Service v1.0
Notes: service of
8.15.1
Recording
/Record/Schedule
/Record/schedule
GET
Viewer
Description
It is used to get recording time range.
Query
None
Inbound Data
None
Success Return
RecordSchedule
PUT
Operator
Description
It is used to update recording time range.
Query
None
Inbound Data
RecordSchedule
Success Return
Notes:
RecordSchedule XML Block

<RecordSchedule version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<enalbled> <enalbled/>
<RecordDelayTime></ RecordDelayTime>
<PreRecordTime></PreRecordTime>
156
<TimeBlock>
<recordType> </recordType>
<dayOfWeek>
</dayOfWeek>
<TimeRange>

<beginTime>
 </beginTime>
<endTime>
 </endTime>
</TimeRange>
</TimeBlock>
</TimeBlockList>
</ RecordSchedule>
8.16 Smart
8.16.1
/Smart/Capabilities
/Smart/capabilities
GET
Description
It is used to get Smart capability.
Query
None
Inbound Data
None
Success Return
<SmartCap>
Notes:
SmartCap XML Block

<SmartCap version="1.0" xmlns=http://www.hikvision.com/ver10/XMLSchema>
<isSupportROI>  </isSupportROI>
<isSupportFaceDetect>  </isSupportFaceDetect>
<isSupportIntelliTrace>  </isSupportIntelliTrace>
<isSupportFieldDetection>  </isSupportFieldDetection>
<isSupportDefocusDetection>  </isSupportDefocusDetection>
<isSupportAudioDetection>  </isSupportAudioDetection>
<isSupportSceneChangeDetection> 
</isSupportSceneChangeDetection>
</SmartCap>

157
8.16.2
/Smart/ROI/channels/ID
/Smart/ROI/channels/ID
GET
Description
Access and configure the ROI for a special channel.
Query
None
Inbound Data
None
Success Return
ROI
PUT
Description
Query
None
Inbound Data
ROI
Success Return
ResponseStatus
DELETE
Description
Query
None
Inbound Data
None
Success Return
ResponseStatus
Notes:
normalizedScreenSize: the size of normalized screen

ROIRegionList:the list of ROI region
<ID> should be consistent with <ID> of streaming.
<enabled/>  if the value of this tag is disable, all of regions are
invalid.
ROI XML Block
<ROI version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id/> 
<enabled/> 
<normalizedScreenSize> 
<normalizedScreenWidth> </normalizedScreenWidth>
<normalizedScreenHeight> </normalizedScreenHeight>
<normalizedScreenSize>
<ROIRegionList/> 
<FaceTrace/> 
<ObjectTrace/> 
</ROI>

158
8.16.3
/Smart/ROI/channels/<ID>/regions
/Smart/ROI/channels/ID/regions
GET
Description
Access and configure the ROI regions for a special channel.
Query
None
Inbound Data
None
Success Return
ROIRegionsList
PUT
Description
Access and configure the ROI regions for a special channel
Query
None
Inbound Data
ROIRegionsList
Success Return
ResponseStatus
Notes:
ROIRegionsList XML Block

<ROIRegionsList version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<ROI/> 
</ROIRegionsList>
8.16.4
/Smart/ROI/channels/<ID>/regions/<ID>
/Smart/ROI/channels/ID/regions/ID
GET
Description
Access and configure one ROI region for a special channel.
Query
None
Inbound Data
None
Success Return
ROIRegion
PUT
Description
Access and configure one ROI region for a special channel
Query
None
Inbound Data
ROIRegion
Success Return
ResponseStatus
DELETE
Description
Access and configure one ROI region for a special channel
Query
None
Inbound Data
None
Success Return
ResponseStatus

159
Notes:
qualityLevel:quality level of a region

RegionCoordinatesList:coordinate of ROI
ROIRegion XML Block
<ROIRegion version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>  </id>
<enabled>
</enabled>
<name>  </name>

<qualityLevelOfROI>
 </qualityLevelOfROI>
<RegionCoordinatesList/>
</ROIRegion>
8.16.5
/Smart/ROI/channels/<ID>/facetrace
/Smart/ROI/channels/ID/facetrace
GET
Description
Query
None
Inbound Data
None
Success Return
FaceTrace
PUT
Description
Query
None
Inbound Data
FaceTrace
Success Return
ResponseStatus
Notes:
FaceTrace XML Block

<FaceTrace version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
</enabled>
<name>  </name>

<qualityLevelOfROI>
</FaceTrace>
 </qualityLevelOfROI>

160
8.16.6
/Smart/ROI/channels/<ID>/objecttrace
/Smart/ROI/channels/ID/objecttrace
GET
Description
Query
None
Inbound Data
None
Success Return
ObjectTrace
PUT
Description
Query
None
Inbound Data
ObjectTrace
Success Return
ResponseStatus
Notes:
ObjectTrace XML Block

<ObjectTrace version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<qualityLevelOfROI>
</ObjectTrace>
8.16.7
</enabled>
 </qualityLevelOfROI>
/Smart/FaceDetect/<ID>
/Smart/FaceDetect/ID
GET
Description
Access and configure the FaceDetect.
Query
None
Inbound Data
None
Success Return
FaceDetect
PUT
Description
Access and configure the FaceDetect.
Query
None
Inbound Data
FaceDetect
Success Return
ResponseStatus
Notes:
<ID> stands for channel number

FaceDetect XML Block
161
<FaceDetect version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>

<id/> 
<enabled>
</enabled>
<minObjectSize>
</minObjectSize>
<maxObjectSize>
</maxObjectSize>
<ROI> 
<minHorizontalResolution>  </minHorizontalResolution>
<minVerticalResolution>
 </minVerticalResolution>
</ROI>
<sensitivityLevel>


</sensitivityLevel>
<detectionThreshold>



</detectionThreshold>
<highlightsenabled> 
</FaceDetect>
8.16.8
</highlightsenabled>
/Smart/IntelliTrace/<ID>
/Smart/IntelliTrace/ID
GET
Description
Query
None
Inbound Data
None
Success Return
IntelliTrace
PUT
Description
Query
None
Inbound Data
IntelliTrace
Success Return
ResponseStatus
Notes:

162
IntelliTrace XML Block

<IntelliTrace version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>  </id>
</enabled>
<tracktime>  </tracktime>
</IntelliTrace>
8.16.9
/Smart/IntelliTrace/<ID>/ZoomRatial
/Smart/IntelliTrace/ID/ZoomRatial
PUT
Description
Query
None
Inbound Data
None
Success Return
ResponseStatus
Notes:
8.16.10 /Smart/FieldDetection/<ID>
/Smart/FieldDetection/ID
GET
Description
Field detection configuration for a video input channels.
Query
None
Inbound Data
None
Success Return
FieldDetection
PUT
Description
Field detection configuration for a video input channels.
Query
None
Inbound Data
FieldDetection
Success Return
ResponseStatus
Notes:
FieldDetection XML Block

<FieldDetection version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>
 </id>
</enabled>
<startTriggerTime>  </startTriggerTime>

163
<endTriggerTime>  </endTriggerTime>

<normalizedScreenSize>
<normalizedScreenWidth>  </normalizedScreenWidth>
<normalizedScreenHeight>  </normalizedScreenHeight>
</normalizedScreenSize>
<minObjectSize>
</minObjectSize>
<maxObjectSize>
</maxObjectSize>
<FieldDetectionRegionList/>
</FieldDetection>
8.16.11 /Smart/FieldDetection/<ID>/regions
/Smart/FieldDetection/ID/regions
GET
Description
Access the list of regions for Field detection on a particular video

input channel.
Query
None
Inbound Data
None
Success Return
FieldDetectionRegionList
PUT
Description

input channel.
Query
None
Inbound Data
FieldDetectionRegionList
Success Return
ResponseStatus
POST
Description

input channel.
Query
None
Inbound Data
None
Success Return
FieldDetectionRegion
DETELE
Description

164
input channel.
Query
None
Inbound Data
None
Success Return
ResponseStatus
Notes:
FieldDetectionRegionsList XML Block

<FieldDetectionRegionList version=1.0
<FieldDetectionRegion/>
</FieldDetectionRegionList>
8.16.12 /Smart/FieldDetection/<ID>/regions/<ID>
/Smart/FieldDetection/ID/regions/ID
GET
Description
Access the list of regions for Field detection.
Query
None
Inbound Data
None
Success Return
PUT
Description
Query
None
Inbound Data
Success Return
ResponseStatus
DELETE
Description
Query
None
Inbound Data
None
Success Return
ResponseStatus
Notes:
FieldDetectionRegion XML Block

<FieldDetectionRegion
<id>
<enabled>
</id>
</enabled>
<sensitivityLevel>

165
version=1.0

</sensitivityLevel>
<timeThreshold>

</timeThreshold>
<objectOccupation>
</objectOccupation>
<RegionCoordinates> 
<positionX>
</positionX>
<positionY>
</positionY>
</FieldDetectionRegion>
8.16.13 /Smart/DefocusDetection/<ID>
/Smart/DefocusDetection/ID
GET
Description
Defocus detection configuration for a audio input channel.
Query
None
Inbound Data
None
Success Return
DefocusDetection
PUT
Description
Defocus detection configuration for a audio input channel.
Query
None
Inbound Data
DefocusDetection
Success Return
ResponseStatus
Notes:
DefocusDetection XML Block

<DefocusDetection version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>
</enabled>
</DefocusDetection>

166
8.16.14 /Smart/AudioDetection/channels/<ID>
/Smart/AudioDetection/channels/ID
GET
Description
Audio detection configuration for a audio input channel.
Query
None
Inbound Data
None
Success Return
AudioDetection
PUT
Description
Audio detection configuration for a audio input channel.
Query
None
Inbound Data
AudioDetection
Success Return
ResponseStatus
Notes:
AudioDetection XML Block

<AudioDetection version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>

</id>
<audioInputException>
<enabled>
</enabled>
</audioInputException>
<soundIntensityMutation>
<enabled>
</enabled>
<sensitivityLevel>
</sensitivityLevel>
<mutationThreshold>

</mutationThreshold>
</soundIntensityMutation>
</AudioDetection>
8.16.15 /Smart/AudioDetection/channels/<ID>/Status
/Smart/AudioDetection/channels/ID/status
GET

167
Description
It is used to get audio strength.
Query
None
Inbound Data
None
Success Return
AudioStrengthStatus
Notes:
AudioStrengthStatus XML Block

<AudioStrengthStatus version=1.0
<id>
</id>
<audioStrength> <!ro, req, xs:integer--> </audioStrength>

</AudioStrengthStatus>
8.16.16 /Smart/SceneChangeDetection/<ID>
/Smart/SceneChangeDetection/ID
GET
Description
Scene change detection configuration for a video input channels.
Query
None
Inbound Data
None
Success Return
SceneChangeDetection
PUT
Description
Scene change detection configuration for a video input channels.
Query
None
Inbound Data
SceneChangeDetection
Success Return
ResponseStatus
Notes:
SceneChangeDetection XML Block

<SceneChangeDetection version=1.0
<id>

</enabled>
<sensitivityLevel>  </sensitivityLevel>
</SceneChangeDetection>

168
Annex A (normative):
XML Schema Definition
A.0 hik.xsd
The following XML Schema Document contains XML schema definitions for data
structures in this specification.
<xs:schema xmlns:hik=http://www.hikvision.com/ver10/XMLSchema
xmlns:xs=http://www.w3.org/2001/XMLSchema
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xmlns:xlink=http://www.w3.org/1999/xlink
targetNamespace=http://www.hikvision.com/ver10/XMLSchema
elementFormDefault=qualified>
<xs:import namespace=http://www.w3.org/1999/xlink schemaLocation=xlink.xsd/>
<xs:annotation>
<xs:documentation>
HIK Core XML Schema
</xs:documentation>
</xs:annotation>

<!-Resource Types
-->

<xs:simpleType name=ResourceType>
<xs:restriction base=xs:string>
<xs:enumeration value=Special Resource />
<xs:enumeration value=Service/>
<xs:enumeration value=General Resource />
</xs:restriction>
</xs:simpleType>

<xs:complexType name=QueryParameter>
<xs:sequence>
<xs:element name=name type=xs:string />
<xs:element name=type type=xs:string />
<xs:element name=description type=xs:string minOccurs=0 maxOccurs=1 />
</xs:sequence>
<xs:complexType>
169


<xs:complexType name=QueryParameterList>
<xs:sequence>
<xs:element name=queryParameter type=hik:QueryParameter minOccurs=0
maxOccurs=unbounded />
</xs:sequence>
<xs:complexType>

<xs:complexType name=OperationParameter>
<xs:sequence>
<xs:element name=description type=xs:string />
<xs:element name=queryParameterList type=hik:QueryParameterList />
<xs:element name=inboundData type=xs:string />
<xs:element name=successReturn type=xs:string />
</xs:sequence>
<xs:complexType>

<xs:complexType name=ResourceDescription>
<xs:sequence>
<xs:element name=version type=xs:string />
<xs:element name=type type=hik:ResourceType />
<xs:element name=get type=hik:OperationParameter minOccurs=0
maxOccurs=1 />
<xs:element name=put type=hik:OperationParameter minOccurs=0
maxOccurs=1 />
<xs:element name=post type=hik:OperationParameter minOccurs=0
maxOccurs=1 />
<xs:element name=delete type=hik:OperationParameter minOccurs=0
maxOccurs=1 />
<xs:element name=notes type=xs:string minOccurs=0
maxOccurs=1 />
</xs:sequence>
<xs:attribute name=version type=xs:string use=required />
<xs:complexType>

<xs:complexType name=Resource>
<xs:sequence>
<xs:element name=version type=xs:string />
<xs:element name=type type=hik:ResourceType />
<xs:element name=description type=xs:string minOccurs=0
maxOccurs=1 />
170
<xs:element name=ResourceList type=hik:ResourceList minOccurs=0

maxOccurs=1 />
</xs:sequence>
<xs:complexType>

<xs:complexType name=ResourceList>
<xs:sequence>
<xs:element name=Resource type=hik:Resource minOccurs=0
maxOccurs=unbounded/>
</xs:sequence>
<xs:complexType>



<xs:simpleType name=StatusCode>
<xs:restriction base=xs:integer>
<xs:minInclusive value=1 />
<xs:maxInclusive value=7 />
</xs:restriction>

</xs:simpleType>

<xs:simpleType name=ID>
<xs:restriction base=xs:integer>
<xs:minInclusive value=1 id=id.minInclusive />
</xs:restriction>
</xs:simpleType>

<xs:complexType name=ResponseStatus>
<xs:sequence>
<xs:element name=requestURL type=xs:anyURI />
<xs:element name=statusCode type=hik:StatusCode />
<xs:element name=statusString type=xs:string />
<xs:element name=id type=hik:ID minOccurs=0 maxOccurs=1 />
</xs:sequence>
</xs:complexType>
</xs:schema>

171
Notes:
- For IP Camera, now only support one input channel. <id> associated with the
input channel can only be 1.
Annex B (Additional content for Encoder)

Hikvision encoders and IPCs share the same HIKCGI protocol documentation, most of the
commands are also suitable for both of encoders and IPCs. But some small difference still
exists between encoders and IPCs. Here I list all of the differences.
Port
You can send PUT /Serial/ports/ID to update the configuration of a serial port supported
by the device. Currently, Hikvision encoders support to configure the parameters of
RS232 port and RS485 port, but RS485 of encoders is placed to PTZ branch
(/PTZ/channels/ID for referance), this is different from IPCs. Please refer to the following
XML Block:
172
SerialPort XML Block

<SerialPort version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>
</id>
<enabled>
</enabled>
<serialPortType> 
</serialPortType>
<baudRate>
</baudRate>
<dataBits>
</dataBits>
<parityType>
<stopBits>

</stopBits>
<workMode>  </workMode>
<flowCtrl>  </flowCtrl>
</SerialPort>
In the above XML Block, <id> only contains 3 and <serialPortType> only contains
RS232. In addition, Hikvision encoders support two kinds of modes: Transparent and
Console; you also can configure the value of flow control of an encoder: none, software or
hardware. So we add two new tags <workMode> and <flowCtrl> at the end of XML Block.
Hivision encoders support multiple video inputs and each video input has two video
streams: main stream and sub stream, so it is not enough to only use digit 1 and digit 2
to indicate all of the streams of an encoder. Currently, we use three digits to indicate the
video stream from a video input. For example, /Streaming/channels/101 indicates the
main stream from the first video channel; /Streaming/channels/202 indicates the sub
stream from the seconde video input. Please refer to the following XML Block:
StreamingChannel XML Block
<id>

</id>
<channelName> 
</channelName>
<enabled>
</enabled>
<Transport>

<rtspPortNo>
</rtspPortNo>
<maxPacketSize>
</maxPacketSize>
<sourcePortNo>
</sourcePortNo>

<ControlProtocol>

<streamingTransport>

</streamingTransport>
173
</ControlProtocol>
<Unicast>

<enabled>

</enabled>
</Unicast>
<Multicast>

<enabled>
</enabled>
<destIPAddress>
</destIPAddress>
<destPortNo>
</destPortNo>
</Multicast>
</Transport>
<Video>
<enabled>
</enabled>
<videoInputChannelID>
</videoInputChannelID>
<videoCodecType>

</videoCodecType>
<videoScanType>  </videoScanType>
<videoResolutionWidth>
</videoResolutionWidth>
<videoResolutionHeight> 
</videoResolutionHeight>
<videoQualityControlType>

</videoQualityControlType>
<constantBitRate> 
</constantBitRate>
<fixedQuality> 
</fixedQuality>
<maxFrameRate> 
</maxFrameRate>
<keyFrameInterval>  </keyFrameInterval>
<BPFrameInterval>  </BPFrameInterval>
<mirrorStatus>  </mirrorStatus>
<rotationDegree> </rotationDegree>
<snapShotImageType> </snapShotImageType>
</Video>
<Audio>
<enabled>

</enabled>
<audioInputChannelID>
</audioInputChannelID>

</Audio>
</StreamingChannel>
In the above XML Block, the values of <id> contain 101, 102, 201, 202,,,, 1501, 1502,
174
1601 and 1602.
Motion Detection Region

When we create a motion detection region, we can set the level of sensitivity. For IPC, the
range of sensitivity is 0-5, 0: the least sensitivity; but for encoder, the range of sensitivity
is 0-6. 0: close; 1: the least sensitivity. Please refer to the following XML Block:
<sensitivityLevel>


</sensitivityLevel>
Trigger
We can send PUT /Event/triggers/ID command to update a particular event trigger
configuration. For IPC, there is only one video input, so if an IPC supports 4-ch alarm
inputs, the allocation rule of ID in URL is as follows:
1 toN is allocated to alarm input port 1 to N;
N+1 is allocated to VMD event;
N+2 is allocated tovideo-loss event;
N+3 is allocated to Shelter alarm event.
For encoder, an encoder may have multiple video inputs, so the allocation rule of ID of an
encoder in URL is as follows:
1 to N is allocated to alarm input port 1 to N;
1 to M is allocated to channel number 1 to M;
IO-N is allocated to IO event;
VMD-M is allocated to VMD event;
Shelteralarm-M is allocated to video-loss event;
Videoloss-M is allocated to Shelter alarm event;
<id>

</id>
<eventType>  </eventType>
<eventDescription>
</eventDescription>
175
<inputIOPortID>
<EventTriggerNotificationList/> 
</EventTrigger>
</inputIOPortID>
Trigger notification
We can send PUT /Event/triggers/ID/notifications/ID to update a particular notification
method and behavior for an event trigger. Taking multiple video inputs of an encoder into
consideration, if the device is an encoder, the allocation rule of two IDs in URL is as
follows:
The first ID in the URI is the string of a trigger.
1 to N are assigned for alarm input port 1 to N
1 to M are assigned for channel number 1 to M
IO-N is assigned for IO event
VMD-M is assigned for VMD event
Shelteralarm-M is assigned for video-loss event
Videoloss-M is assigned for Shelter alarm event
The second ID in the URI is the string of a notification.
1 to N are assigned for alarm output port 1 to N
1 to M are assigned for channel number 1 to M
1 to K are assigned for preset number 1 to K
1 to P are assigned for pattern number 1 to P
1 to Q are assigned for patrol number 1 to Q
IO-N is assigned for IO notification
record-M is assigned for record notification
ptzM-presetK is assigned for preset notification
ptzM-patternP is assigned for pattern notification
ptzM-patrolQ is assigned for patrol notification
beep is assigned for beep notification
email is assigned for email notification
monitorAlarm is assigned for monitorAlarm notification
center is assigned for upload information to center notification
FTP is assigned for upload picture to FTP server notification
EventTriggerNotification XML Block

<EventTriggerNotification version=1.0
176
<id>
</id>
<notificationMethod></notificationM
ethod>
<notificationRecurrence> 
</notificationRecurrence>
<outputIOPortID>

</outputIOPortID>
<ptzAction> 
<ptzChannelID>  </ptzChannelID>
<actionName>  </actionName>
<actionNum>  </controlProtocol>
<controlAddress>
 </controlAddress>
<PresetIDList> <! opt -->
<PresetID> <! opt -->

177

</PresetID>
</PresetIDList >
<PatrolIDList> <! opt -->
<PatrolID> <! opt -->
</PatrolID>
</PatrolIDList >
<PatternIDList> <! opt -->
<PatternID> <! opt -->
</PatternID>
</PatternIDList>
<PTZRs485Para>
<baudRate>
</baudRate>
<dataBits>
</dataBits>
<parityType>
<stopBits>

</stopBits>
<flowCtrl>  </flowCtrl>
</PTZRs485Para>
</PTZChannel>
/Audio/channels/ID
Hikvision encoders support multiple audio inputs. For IPC, the value of <id> is 1. But the
value of <id> for encoders is 1, 2, 3, maxChanNum, as follows:
AudioChannel XML Block
<AudioChannel version=1.0 xmlns=http://www.hikvision.com/ver10/XMLSchema>
<id>

</id>
<enabled>
</enabled>
<audioMode>

</audioMode>
<microphoneEnabled> 
</microphoneEnabled>
<microphoneSource>

</microphoneSource>
<microphoneVolume> 
</microphoneVolume>
<speakerEnabled>
</speakerEnabled>
178
<speakerVolume>
</AudioChannel>

</speakerVolume>
Currently, Hikvision encoders only support /Image/channels/<ID>/Color command, other
nodes, such as WDR, BLC, Shutter and so on dont support.

179

Hik Ipmd V2.0 201404

Uploaded by

Copyright:

Available Formats

Hik Ipmd V2.0 201404

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hik Ipmd V2.0 201404

Uploaded by

Copyright:

Available Formats

IP Media Device Management Protocol

COPYRIGHT 2009, Hikvision Digital Technology Co., Ltd

Finished the Mandatory services

Update the /PTZ/channels/ID/PTZControl resources

Amend the DDNS related resources; add the

The <Zeroconf> tag is supported in the block XML of

Add resourceCustom/HIKCGI/Event/ schedule/ ID.

New resource /System/Storage is defined

2009 2014 by HIKVISION. All rights reserved.

New service /PTZCtrl is defined

Service /Image/channels/<ID>/IrcutFilter has been

2009 2014 by HIKVISION. All rights reserved.

Added <exposureMode> tag and <WDREnabled> tag

New service /Smart branch is defined

2009 2014 by HIKVISION. All rights reserved.

Update the /System/fisheye resources

COPYRIGHT, Hikvision Digital Technology Co., Ltd

2009 2014 by HIKVISION. All rights reserved.

8.1.13 Storage ........................................................................................................... 29

8.11.12 Notification alertStream ............................................................................... 99

8.13.34 /PTZCtrl/channels/<ID>/timetasks ........................................................... 128

Record ........................................................................................................................... 156

References are either specific (identified by date of publication, edition number,

For a specific reference, subsequent revisions do not apply.

For a non-specific reference, the latest version applies.

RFC2616 Hypertext Transfer Protocol-HTTP/1.1

2009 2014 by HIKVISION. All rights reserved.

3 Definitions and abbreviations

Fully Qualified Domain Name

4.1 REST and HTTP Methods

Collection URI, such as

Member URI, such as

4.3 Resources overview

Configure and operate the general system

Configure network interfaces.

Configure the Input/Output (IO).

Handle video-related configuration.

Configure the Audio.

Control two ways audio.

Configure and control the Serial ports.

Two way audio

2009 2014 by HIKVISION. All rights reserved.

Provide Security functions.

Configure and control the streaming media

Configure and control the motion detection of the

Provide event notification functions.

Control the device pan tilt and zoom.

Configure and control PTZ.

Configure front-end parameters.

Configure recording schedule.

Configure smart event parameters.

4.4 Protocol URL

2009 2014 by HIKVISION. All rights reserved.

4.5.1Connection Header Field

4.5.2Authorization and WWW-Authenticate Header

HTTP Request Message:

2009 2014 by HIKVISION. All rights reserved.

HTTP Response Message:

Content-Type: application/xml; charset=UTF-8