From what I've read in the 3.7 docs:
The JSON variant of the HTTP data point contains two additional fields: the device identifier key and the device identifier itself. These are formed from the use case where a device publishes its name in the JSON object, i.e. "id":"eGauge42", where "id" is the key and "eGauge42" is the identifier. The other properties are inherited from the HTTP Receiver data point properties. If the device identifier key is left blank, the receiver will behave as though every JSON object corresponds to the point.
If you're using receive type 2, then you can also specify a Jackson JSON path to a number of milliseconds epoch timestamp. The device identifier key, parameter name, and timestamp key are all Jackson JSON paths within the received Json object.
And to expand regarding your timestamp question:
Timestamps can be represented in multiple ways. If a timestamp is detected (i.e. is not empty), Mango will attempt to parse it first in the format "yyyyMMddHHmmss", then "yyyy-MM-dd'T'HH:mm:ss'Z'", and finally as a UTC millisecond count since midnight on Jan 1, 1970. (See the "Date/time formats" documentation for more information.)
__device – the device ID of the sender
__time – the time override
__point – the prefix which provides an with which an alternate method of providing a point name. The characters following the prefix must match the characters that follow a '__value' parameter prefix. The characters that follow the prefix are used for matching only, and are otherwise insignificant.
__value – the prefix which provides the corresponding value for a key given with a '__point' prefix.
Basically use a __time parameter and give an ISO timestamp or an epoch timestamp. Alternatively, use the JSON path notation and tell it what your timestamp is in epoch milliseconds.
Hope that shines some light on the situation. if you can, fire your request into https://webhook.site and perhaps copy the request here if you still encounter issues.
Best of luck!
Fox
