| GET | /sensor/vpn/register/v3/tag | ||
|---|---|---|---|
| POST | /sensor/vpn/register/v3/tag |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| name | body | string | Yes | host |
| device | body | string | Yes | device |
| subdevice | body | string | Yes | subdevice |
| location | body | string | Yes | location |
| latitude | body | double | Yes | latitude |
| altitude | body | double | Yes | altitude |
| longitude | body | double | Yes | logitude |
| tag | body | int | Yes | tag |
| distance | body | double | Yes | distance |
| rfid | body | int | Yes | rfid |
| angle | body | double | Yes | angle |
| mIndex | body | int | Yes | mIndex |
| battery | body | double | Yes | battery |
| methode | body | string | Yes | methode |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /sensor/vpn/register/v3/tag HTTP/1.1
Host: 188.138.100.94
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<ccsVpnRegisterDeviceTag xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/ccsService">
<altitude>0</altitude>
<angle>0</angle>
<battery>0</battery>
<device>String</device>
<distance>0</distance>
<latitude>0</latitude>
<location>String</location>
<longitude>0</longitude>
<mIndex>0</mIndex>
<methode>String</methode>
<name>String</name>
<rfid>0</rfid>
<subdevice>String</subdevice>
<tag>0</tag>
</ccsVpnRegisterDeviceTag>