EMFIT QS™
Cloud API
Technical integration overview for research organizations
EMFIT QS™ research data can be integrated directly into a research organization’s own systems and data infrastructure.
Depending on the study requirements, data can be delivered automatically through EMFIT Cloud using push-based APIs, retrieved when needed, or transferred directly to the organization’s own cloud storage or SFTP environment.
The available interfaces include:
Sleep Period API · Live Data API · Status API · Raw Signal API
For an overview of the physiological, sleep, movement and waveform data available from EMFIT QS™, please see the EMFIT QS™ Research and Organizational Use page.
Technical integration overview for research organizations
No continuous polling required
EMFIT Cloud can automatically deliver processed and live data to the research organization’s own HTTPS endpoint.
The following interfaces use push-based delivery:
Live Data API
Provides heart rate, respiratory rate, activity and tossing-and-turning data during an ongoing measurement period. By default, data is delivered every 30 seconds. Selected events can be delivered immediately when they occur.
Status API
Provides current device and measurement status, including connectivity, bed presence status, status duration and last received data information.
Sleep Period API
Provides a complete processed dataset after a sleep or presence period has ended and post-processing has been completed. Fixed processing periods of 6, 8, 12 or 24 hours can also be configured when required by the study protocol.
Data is delivered in structured JSON format to an endpoint provided by the research organization.
Live data and event delivery
Data during an ongoing measurement
The Live Data API is intended for applications that require access to data before the current sleep period has ended.
Typical live data includes:
- Heart rate
- Respiratory rate
- Movement activity
- Tossing and turning
The default delivery interval is 30 seconds. Selected events can be pushed without waiting for the next periodic data transmission.
For special integrations, additional data can also be made available according to the study requirements.
Status information
Distinguish participant status from connectivity status
The Status API provides a separate view of the current system state.
Status information can include:
- Whether the device is connected to EMFIT Cloud
- Whether the participant is in bed or out of bed
- Undeployed status
- Network error status
- Sensor error status
- How long the current status has continued
- When data was last received from the device
This can be particularly useful in remote and longitudinal studies, where researchers may need to distinguish between a participant simply being out of bed and missing data caused by a connectivity or device issue.
Processed Sleep Period data
Complete post-processed datasets
The Sleep Period API provides a processed dataset after the recorded sleep or presence period has ended.
The dataset can include physiological time-series data, sleep staging, HRV and ANS parameters, bed-exit and movement events, sleep-period summaries and other calculated metrics.
Sleep Period data can also be generated using fixed processing periods of 6, 8, 12 or 24 hours, with a configurable start time, when this better matches the research protocol.
For a detailed description of available data and resolutions, please refer to the EMFIT QS™ Research and Organizational Use page.
Raw Signal API
Access BCG waveform data for independent analysis
Researchers who want to perform their own signal processing can retrieve BCG waveform data through the Raw Signal API.
Unlike the push-based Live, Status and Sleep Period interfaces, raw signal retrieval is based on HTTPS GET requests. The receiving system first obtains the list of available raw-signal periods and then retrieves the required dataset.
For research use, the waveform data is provided in EDF format.
The EDF file contains the original signal bands received by the EMFIT servers without additional server-side filtering. Depending on the device configuration, waveform sampling is available at 100 Hz, with 200 Hz available in special configurations.
This allows research teams to perform their own signal processing, algorithm development and validation independently of EMFIT’s calculated physiological and sleep parameters.
Direct delivery to your data infrastructure
AWS S3 · Azure Blob Storage · SFTP
For larger studies and higher-volume datasets, EMFIT can transfer data directly to the research organization’s own storage environment.
Supported destinations include:
AWS S3
Azure Blob Storage
SFTP
All types of study data can be delivered directly to these storage services when configured for the project. The API documentation identifies this as a preferred delivery option for many file-based research integrations.
This approach can be particularly useful for:
- Large multi-participant studies
- High-frequency waveform data
- Longitudinal data collection
- Automated research data pipelines
- Environments where file-based ingestion is preferred over webhook processing
Data formats
Different formats are used depending on the type of data:
JSON
Processed Sleep Period data, Live Data, Status information and events
EDF
BCG waveform data for independent signal analysis
The data-delivery architecture and file naming can be configured according to the requirements of the study and receiving system.
Data formats
Multiple authentication and transfer options
EMFIT Cloud integrations can be configured with security controls appropriate for the receiving organization.
Depending on the integration model, supported approaches include:
- IP allowlisting
- Secure token authentication
- Custom HTTPS authorization headers
- Server-to-server OAuth authorization
These methods are described in the EMFIT QS API specification.
For file-based delivery, datasets can optionally be:
- compressed using gzip
- encrypted using AES-256
- protected using a separately encrypted random key based on the research organization’s public key
The appropriate security and data-delivery configuration is agreed during integration setup.
Flexible integration architecture
EMFIT QS™ can therefore support several different integration models:
Real-time or near-real-time studies
Live Data and event delivery to the organization’s endpoint
Longitudinal sleep research
Processed Sleep Period datasets after each completed measurement period
Remote deployment monitoring
Status API for participant/device status and connectivity
Signal-processing research
Raw BCG waveform data in EDF format
Large-scale studies
Direct delivery to AWS S3, Azure Blob Storage or SFTP
One or several interfaces can be used together depending on the research protocol.
Detailed technical documentation
Detailed API documentation, including endpoint specifications, payload structures, field descriptions, authentication details and integration examples, is provided to research customers during technical integration.
Use of the EMFIT QS™ APIs is subject to the applicable service agreement, Terms of Service and API License Terms.
Please Note: The specifications listed above are subject to change without prior notice as we continually strive to enhance and improve our products. We reserve the right to modify specifications as needed to ensure the highest quality and performance. For the most up-to-date information, please contact our customer support team.
Planning an integration?
Tell us about your study, required data, deployment scale and preferred data-delivery architecture.
We can help determine the most suitable API and data-delivery configuration before study deployment.