flespi HTTP channel protocol by Gurtam is used to receive messages in a POST HTTP request in the same format as a flespi stream with protocol HTTP. It can help you to involve all flespi pipeline (like devices and streams) to handle your data from any projects including IoT.

The body of POST HTTP request should contain a JSON array with message objects. You may set JSON-path (dot-separated path to JSON-array of messages) if the HTTP body is JSON object. Each message object should contain an ident string property plus any additional properties. You may set another field to use as an ident in the channel configuration. The value of timestamp property (if present) should be a number with Unix time, or UTC time string in full ISO 8601 format (YYYY-MM-DDThh:mm:ss).

Below is the list of parameters that can appear in the messages received by the channel via http protocol. In most parameters, the name consists of tags split by dots: tag1.tag2.tag3.tag4... Each tag defines a certain area of an application, e.g. any parameter that contains mileage data has the 'mileage' tag in the name and any parameter related to fuel control contains the 'fuel' tag. By default JSON fields of the message received by a channel via this protocol can only contain the below-specified parameters. Any additional parameter will be prefixed by the "custom" tag, e.g. "custom.unspecified-name".

Name Type Unit Description number ID of channel that received a message
custom Any custom parameter number ID of device that received a message string Name of device that received a message number ID of device type of device that received a message
ident string Device unique identificator and optional password number ID of protocol
server.timestamp number seconds Timestamp when server received a message
timestamp number seconds Message timestamp
No results found.