eView device data via API

Obtain telematics data from eView devices via API in 5 easy steps.

Obtain telematics data from eView devices via API in 5 easy steps:

  1. Create a free flespi account.

  2. Set up the eView channel in your flespi.io interface.

  3. Point a eView device to your flespi account using the configurator from eView or by sending an SMS command to the device.

  4. Confirm that the device data is being received and parsed.

  5. Access eView device data via API.

  6. [OPTIONAL] Create a flespi device to access telemetry, apply plugins and analytics, and use long-term message storage.

1. Create a free flespi account

(a) Go to www.flespi.io and click on LOGIN / REGISTER:

flespi login page

(b) You can choose from a number of third-party service accounts to log in under or the right-most option @ to register with your name and email address: 

flespi login method

2. Set up the eView channel in your flespi.io interface:
(a) Click on Telematics Hub (1), then on Channels (2), then on the plus button in the lower right corner of the screen (3).

flespi channels section

(b) Channel dialogue box will come up. Enter the name for the channel (any text will suffice) (1), select “eView” in the protocol_id drop-down (2), click SAVE + OPEN (3):

create eview channel flespi

(c) Channel dialogue will open. Make a note of the domain name and port that you should point your device to. IMPORTANT: Image below indicates where to find the info and is NOT an actual domain/port for you to use.

flespi eview channel domain name port

3. Point your eView device to your flespi account using an SMS command to the device (syntax is provided below). The domain name and port to point the device to are shown in the channel box.

Syntax of the SMS command is as follows:

IP1,<domain name>,<port>

4. Confirm that the device data is being received and parsed:

Confirm that the device data is being received and parsed. Ensure that the LOGS & MESSAGES tab is selected. Also, option BOTH right below should also be selected. Inspect log records (1) to confirm that your device has successfully connected to flespi. The presence of messages in the lower half of the screen (2) will confirm that the incoming data is parsed.

flespi eview channel logs messages

In case of any issues, check out our troubleshooting checklist.

5. Access eView device data via API:

(a) Click on the REST API Documentation menu item in the lower-left corner:

flespi panel open rest api docs

(b) In the menu on the right under Gateway API click on channels:

flespi rest api gateway

(c) Scroll down until you see GET /channels/{1-ch-selector}/messages request. Click on it to reveal additional fields. 

flespi rest api get channel messages

(d) Put in your channel ID into the 1-ch-selector field (1) and execute the API call (2).

flespi rest api get channel messages execute

(e) And here you have it. eView device messages in an easy to read JSON format:

flespi rest api get eview channel messages result

6. [OPTIONAL] Create a flespi device. This step takes interaction with your device on a qualitatively new level — get access to device telemetry, easily send configuration commands, configure post-processing using plugins, aggregate messages into intervals, benefit from extended message storage.

Click on Telematics Hub (1), then on Devices (2), then on the plus button (3) in the lower right corner of the screen (3). Pick the proper device type and specify the device ID:

create flespi device queclink

Now you can use the device API to access device data, send commands, and a lot more, or explore the numerous tabs on the device card.

What's next?