...
message_trace_id - a message trace id;
message_time - a time of receiving a message from a base stations;
received_time - a time of receiving a message by the Nwave cloud;
device_id - a device ID in hex decimal format ;
modem_id - q a device ID in decimal hex format;
signal - a message signal level;
data - a raw message payload in hex format;
station_id - an ID of a station which got the message;
custom_id - a bound position custom ID or '?' if a custom ID was not set;
latitude - a latitude parameter of a position;
longitude - a longitude parameter of a position;
level - position's level (e.g. ground, 1st);
network_id - a network ID of a position;
zone_id - a decimal zone ID of a position;
group_id - a decimal group ID of a position;
group_name - a group name which a position belongs to;
group_inner_id - an inner ID of a position in a group;
parsed - a parsed message. It contains different data, depending on device type, firmware type and message type.
...
For retrieving a value of any field from source data you need to use source data field name surrounded by braces. This rule works for all fields except of parsed data fields . For retrieving any value from parsed data you need to use the following format: {parsed['<field name>']}.
Examples:
{devicemodem_id}- gets device ID hex;{data}- gets full raw message;{message_time}- gets a UNIX timestamp;{parsed['voltage_V']}- gets battery voltage information.
...
For more examples, you can read Sensor Heartbeat/Status Change API with Basic Authorization Standard Outgoing Protocol and other standard protocols.
...