This article provides information abou the best EloView Web APIs out of the EloView DevZone

When testing EloView web APIs outside of the DevZone, make sure to include all required parameters in the header, including the authPayload.  Within the EloView DevZone, authPayload is passed along automatically but outside of the DevZone, you will need to explicitly specify this parameter.

In the below example, we are using the EloView reboot API to send a request from Postman (www.Postman.com) to reboot a specific device:

Prerequisites (to be completed in EloView):

• Use the EloView Authorization API to generate your userID, orgID, and authPayload
• The serial number(s) for your Elo Android test device
• Use the EloView Reboot Device API (requires userID and orgID) to generate the request URL which includes userID, orgID, and reboot command

In Postman, specify the following:

1. Using the POST method, copy/paste or specify the following request URL: 

• https://manage.eloview.com/restapi/user:id=YOUR_USERID/org:id=YOUR_ORGID/reboot#2.0.0

2. In the Header:

• content-type: application/json
• accept: application/json
• accept-version: 2.0.0
• authpayload: ***** (Note: copy authpayload received from EloView DevZone Authorization API)

3. In the Body, specify the device serial number:



4. After sending the request, you get the “Reboot Successful” response.



If you receive a 401 authorization error, go back to the EloView DevZone and run the authentication API again.  This will generate a new authPayload for use.  The userID and orgID should be the same.