Data Push Webhook Service

Describe

The data push service is mainly used to meet the needs of customers for secondary development of basic devices data. This function can realize the active push of devices location data, alarm data, event data, offline/online status data, and data issued by commands.
1. First, you need to write a WEB API interface based on the POST method to receive the data forwarded by the server. Please refer to the client code example
2. Configure the written WEBAPI address through the rule ->Create a new rule, and fill it into the client address, which corresponds to the full URL of the interface, such as: http://47.112.122.222:8080/revTerminalLocation
3. After the rules are configured, they are expected to take effect automatically within 5 minutes. At this time, the device reports the data, and the system's push engine will forward the data to the configured client address.

Rule Configuration

The user can configure the data to be pushed by the specified company in the rule configuration interface. The user needs to configure the data type, client address and other information.
If there is a message header restriction, you need to add the message header configuration. If not, you can ignore it.

Data type specification

1.Positioning data

Device positioning data, including Device ID, positioning time, longitude and latitude, speed, mileage and other information

JSON String Example

  {"assetId":"8022300001","longitude":0.0,"latitude":0.0,"speed":0,"direction":0,"mileage":16,"gpsTime":"2022-09-01T08:59:56Z","recvTime":"2022-09-01T08:59:56.964Z","locType":0,"cellSignal":19,"gnssSignal":0,"cells":"460,0,9383,220792647","battery":100,"voltage":"0.0","statusJson":"{\"lockBar\":-1,\"lockRope\":0,\"lockStatus\":0}","expandInfo":"{\"angle\":\"null\",\"backBattery\":\"null\",\"fuels\":\"-1,-1,-1\",\"humidity\":\"0\",\"lux\":\"0.0\",\"networkType\":\"0\",\"pressure\":\"0.0\",\"reportType\":\"0\",\"temperature\":\"-1000.0\"}"}

Json Field Description

Lock Status JSON Description

Vehicle status JSON description

JSON description of extension information

2.Alarm data

Alarm data generated by equipment, including equipment number, alarm type, alarm time, longitude and latitude, etc.

Push JSON Example

{"assetId":"875011000025","alarmType":46,"dateTime":"2020-04-01T00:00:13Z","longitude":0.0,"latitude":0.0,"speed":0,"mileage":0,"cells":"0,0,0,0","describe":"","fileIndex":"1585699212"}

Json Field Description

Alarm Type Description：

3.Event data

Event data generated by Device, including Device ID, event type, time, longitude and latitude, etc.

Push JSON Example

{"assetId":"795206001104","eventType":1,"unLockType":1,"dateTime":"2022-08-19T02:07:28Z","longitude":0.0,"latitude":0.0,"speed":0,"mileage":5,"cells":"460,0,10352,220726855","card":"0003116836","password":"","describe":"{"waybillGUID":"190db1a2-3df1-4857-b94e-ee5937334409","waybillNo":"45435345"}}

Json Field Description

Event Type Description：

4.Command response data

Command response data generated by the device, including device number, command type, time, and returned content information of the command.

Push JSON Example

{"assetId":"742207000010","commandType":"BASE2","content":"[\"742207000010\",\"8\",\"001\",\"BASE\",\"2\",\"20220901081402\"]","dateTime":"2022-09-01T08:14:03.564Z"}

Json Field Description

5.Slave lock(sensor)

 Slave Device positioning data, including Device ID, positioning time, longitude and latitude, speed, mileage and other information

JSON String Description

  {"assetId":"8012600005","longitude":113.92294,"latitude":22.670017,"speed":0,"direction":0,"gpsTime":"2023-12-07T08:30:31Z","recvTime":"2023-12-07T08:30:52.474Z","subGpsTime":"2023-12-07T08:29:50Z","battery":71,"voltage":"3.93","subAssetID":"E0171E0365","sensorType":4,"statusJson":"{\"lockRope\":0,\"gateway\":0}","locStatus":0,"locRope":0,"rssi":57,"temperature":-1000.0,"humidity":0,"eventType":6,"locTimes":5,"subGpsTimestamp":1701937790000}

JsonField Description

statusJson Field Description

“FStatusJson”:”{"bottomDisassembly":0,"emergencyKey":0,"lockMotor":0,"structuralDisassembly":0,"gateway":0,"lockValve":0}”

Push log report

After configuring the push rules, users can query the logs generated by the platform’s active push in the push log to facilitate problem analysis.