Skip to main content

API Introduction

The LAMP API provides programmatic access to all data and configuration in the mindLAMP platform. The API follows a hierarchical object model and uses HTTP Basic Auth for all requests.

Object Modelโ€‹

The LAMP Platform organizes data in a hierarchy:

Server Administrator
โ””โ”€โ”€ Researcher / Clinician
โ””โ”€โ”€ Study / Group
โ”œโ”€โ”€ Activity โ†’ ActivitySpec (schema)
โ”œโ”€โ”€ Sensor โ†’ SensorSpec (schema)
โ””โ”€โ”€ Participant
โ”œโ”€โ”€ ActivityEvent (time-series)
โ””โ”€โ”€ SensorEvent (time-series)
  • Researchers/Clinicians manage studies and participants.
  • Studies/Groups contain activities, sensors, and participants.
  • ActivitySpecs and SensorSpecs are global schemas defining the structure of activities and sensors.
  • Events are time-series data points owned by a participant and linked to an activity or sensor.
  • Tags are arbitrary key-value metadata that can be attached to any object.

Authenticationโ€‹

All API requests use HTTP Basic Auth. The scope of accessible data depends on the credential level:

  • Server Administrator โ€” Access to everything.
  • Researcher/Clinician โ€” Access to their own groups and participants.
  • Participant โ€” Access to their own data only.

API Referenceโ€‹

The full interactive API reference is available at /api, generated from the OpenAPI specification. You can test API calls directly from the documentation.

Data Formatโ€‹

All events follow a consistent format with a timestamp, a sensor/activity identifier, and a data payload. See Data Types Reference for schemas.