Http protocol

Integration level: params
The easiest protocol for pushing telematics data to flespi. Channel with this protocol can receive messages via POST HTTP requests.
flespi parses the Http protocol messages into a JSON object with the fields listed below in the Parameters tab.
channel.id
number
ID of channel that received a message
custom
Any custom parameter
device.id
number
ID of device that received a message
device.name
string
Name of device that received a message
device.type.id
number
ID of device type of device that received a message
ident
string
Device unique identificator and optional password
protocol.id
number
ID of protocol
server.timestamp
number
seconds
Timestamp when server received a message
timestamp
number
seconds
Message timestamp

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 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).