Telematics and Connected Mobility conference 
September 10–11, 2025 / Vilnius, Lithuania
September 10–11, 2025 / Vilnius, Lithuania
Usage specifics
Parameters (41)
ScoutOpen 2
Flespi parses telemetry data from your ScoutOpen 2 into a standardized JSON and
lets you send commands to ScoutOpen 2 via API.
Here’s the like of JSON you get
{
"ident": "352625333222111",
"position.altitude": 273.61,
"position.hdop": 0.7,
"position.latitude": 49.069782,
"position.longitude": 28.632826,
"position.satellites": 18,
"server.timestamp": 1650636570.426424,
"timestamp": 1650636570.426424,
"device.type.id": "ScoutOpen 2",
"channel.id": 1111,
"protocol.id": "scout-open-2"
"engine.ignition.status": true
...
}
How to consume this nice JSON
The easiest way is to make a REST API request like this
curl -X GET --header 'Authorization: FlespiToken XXX' 'https://flespi.io/gw/devices/<device id>/messages'
You can also
Modify messages
Add or remove parameters, inject data from LBS and reverse-geocoding services, etc.
Learn what plugins can do
Aggregate data
Determine trips and stops, catch events, detect geofence ins/outs, and more.
Learn about flespi analytics capabilities acceleration.array
array
g
Array of objects with acceleration data by x, y, and z axis
average.x.acceleration
number
g
Harsh acceleration event average accelerometer value on X-axis
average.y.acceleration
number
g
Harsh acceleration event average accelerometer value on Y-axis
backup.battery.status
boolean
Backup battery usage status
channel.id
number
ID of channel that received a message
crash.completed.status
boolean
Last block with accident data
crash.data.offset
number
Offset of the acceleration block from the beginning of the array
crash.id
number
Crash ID
crash.timestamp
number
Crash timestamp
custom
any
Any custom parameter
device.id
number
ID of device that received a message
device.imei
string
IMEI of the device
device.name
string
Name of device that received a message
device.type.id
number
ID of device type of device that received a message
eco.driving.event.duration
number
seconds
Duration of event that did generate Green driving
engine.ignition.status
boolean
Engine ignition or ACC status
hardware.version.enum
number
Hardware version enum
harsh.acceleration.event
boolean
Harsh acceleration detected
harsh.cornering.event
boolean
Harsh cornering detected
ident
string
Device unique identifier like serial number, IMEI, etc
max.x.acceleration
number
g
Harsh acceleration event max accelerometer value on X-axis
max.y.acceleration
number
g
Harsh acceleration event max accelerometer value on Y-axis
movement.status
boolean
Current movement state
peer
string
IP:port from which device connecting to the channel
position.altitude
number
meters
Altitude value for position
position.direction
number
degrees
Heading angle at position detection moment
position.hdop
number
Horizontal dilution of precision
position.latitude
number
degrees
Latitude coordinate value
position.longitude
number
degrees
Longitude coordinate value
position.pdop
number
Position dilution of precision
position.satellites
number
Quantity of satellites used to calculate coordinates for given position information
position.speed
number
km/h
Instant speed at position detection moment
position.valid
boolean
Is position information accurate and valid for given timestamp
position.vdop
number
Vertical dilution of precision
protocol.id
number
ID of protocol
server.timestamp
number
seconds
Timestamp when server received a message
timestamp
number
seconds
Message timestamp
timestamp.key
number
Message timestamp in seconds with message sequence number appended as the value fractional part. Used to distinguish between several messages that have the same timestamp.
vehicle.mileage
number
km
Total calculated mileage
x.acceleration
number
g
Accelerometer value X
y.acceleration
number
g
Accelerometer value Y