Activities

https://api.lumobodytech.com/v1/users/me/activities?start_time=1397708448&end_time=1397709448&data_source=LUMO_LIFT&offset=1397719448 This endpoint returns all activity data for each 5 minute interval within the requested time range. In other words, this endpoint effectively combines the data from all the other endpoints below.

Steps

https://api.lumobodytech.com/v1/users/me/activities/steps?start_time=1397708448&end_time=1397709448&data_source=LUMO_LIFT&offset=1397719448

This endpoint returns the total and running specific steps taken by a user for each 5 minute interval within the requested time range. The start_time and end_time parameters are Unix timestamps specifying local times for the requested user. The data_source parameter allows filtering for data coming from a specific Lumo compatible application. Currently, the two allowed values for this parameter are LUMO_BACK and LUMO_LIFT. If you develop your own mobile Lumo app and register an app id, you will be able to specify that app id as your data_source and thus effectively use the Lumo backend to store and retrieve your app’s data. The offset parameter is used for pagination and should be set to the value of the ‘next’ field in the metadata part of the response. When there are no additional results left in the requested time range, ‘next’ will be equal to 0.

If no RUNNING_STEPS data is returned for a given 5 minute interval, you can assume the value is 0. To determine the number of walking steps taken in a 5 minute interval subtract RUNNING_STEPS from TOTAL_STEPS.

{ "data": [
{ "dataSource": "LUMO_LIFT", "dataType": "TOTAL_STEPS", "localTime": 1391689500, "value": 8 },
{ "dataSource": "LUMO_LIFT", "dataType": "RUNNING_STEPS", "localTime": 1391690400, "value": 31 }],
"metadata": { "next": 0 } }

Distance

https://api.lumobodytech.com/v1/users/me/activities/distance?start_time=1397708448&end_time=1397709448&data_source=LUMO_LIFT&offset=1397719448

This endpoint returns the total and running specific distance traveled by a user for each 5 minute interval within the requested time range. The start_time and end_time parameters are Unix timestamps specifying local times for the requested user. The data_source parameter allows filtering for data coming from a specific Lumo compatible application. Currently, the two allowed values for this parameter are LUMO_BACK and LUMO_LIFT. If you develop your own mobile Lumo app and register an app id, you will be able to specify that app id as your data_source and thus effectively use the Lumo backend to store and retrieve your app’s data.

If no RUNNING_DISTANCE data is returned for a given 5 minute interval, you can assume the value is 0. To determine the number of walking steps taken in a 5 minute interval subtract RUNNING_DISTANCE from TOTAL_DISTANCE. The value here is in units of meters.

{ "data": [
{ "dataSource": "LUMO_LIFT", "dataType": "TOTAL_DISTANCE", "localTime": 1391689500, "value": 6 },
{ "dataSource": "LUMO_LIFT", "dataType": "RUNNING_DISTANCE", "localTime": 1391690400, "value": 24 },  ],
"metadata": { "next": 0 } }

Calories

https://api.lumobodytech.com/v1/users/me/activities/calories?start_time=1397708448&end_time=1397709448&data_source=LUMO_LIFT&offset=1397719448

This endpoint returns the calories burned by a user for each 5 minute interval within the requested time range. The start_time and end_time parameters are Unix timestamps specifying local times for the requested user. The data_source parameter allows filtering for data coming from a specific Lumo compatible application. Currently, the two allowed values for this parameter are LUMO_BACK and LUMO_LIFT. If you develop your own mobile Lumo app and register an app id, you will be able to specify that app id as your data_source and thus effectively use the Lumo backend to store and retrieve your app’s data. Calories are burned by running, walking, and by the sum of all activity that is not running or walking(sitting, standing,etc.) To determine the number of calories expended by anything other than walking or running, perform this calculation for a given 5 minute interval: TOTAL_CALORIES - (WALKING_CALORIES + RUNNING_CALORIES)

{ "data": [
{ "dataSource": "LUMO_LIFT", "dataType": "TOTAL_CALORIES", "localTime": 1391689500, "value": 6 },
{ "dataSource": "LUMO_LIFT", "dataType": "WALKING_CALORIES", "localTime": 1391689500, "value": 0 } ],
{ "dataSource": "LUMO_LIFT", "dataType": "RUNNING_CALORIES", "localTime": 1391689500, "value": 10 } ],
"metadata": { "next": 0 } }

Posture

https://api.lumobodytech.com/v1/users/me/activities/posture?start_time=1397708448&end_time=1397709448&data_source=LUMO_LIFT&offset=1397719448

This endpoint returns the number of seconds a user spent in a given type of posture for each 5 minute interval within the requested time range. The start_time and end_time parameters are Unix timestamps specifying local times for the requested user. The data_source parameter allows filtering for data coming from a specific Lumo compatible application. Currently, the two allowed values for this parameter are LUMO_BACK and LUMO_LIFT. If you develop your own mobile Lumo app and register an app id, you will be able to specify that app id as your data_source and thus effectively use the Lumo backend to store and retrieve your app’s data. The possible

The possible posture type values for Lumo Lift are:

"TIME_IN_GOOD_POSTURE",
"TIME_IN_BAD_POSTURE"

A typical response from a Lumo Lift dataSource might look like:

{ "data": [
{ "dataSource": "LUMO_LIFT", "dataType": "TIME_IN_GOOD_POSTURE", "value": 111, "localTime": 1391689500 },
{ "dataSource": "LUMO_LIFT", "dataType": "TIME_IN_BAD_POSTURE", "value": 289, "localTime": 1391689500 } ],
"metadata": { "next": 0 } }