Emfit QS
Cloud API Overview

Emfit provides two main ways for customers to automatically access data from QS sleep sensors via the cloud:

1. Push API (Sleep Summaries and Live Data)

• We can automatically send processed data to your system as soon as it’s available — no polling required.
• Sleep Summary Data: Delivered once a user gets out of bed and the full sleep period is processed (approx. 5–20 min delay).
• Live Data (optional) and events: Heart rate, respiration rate, and movement data every 30 seconds; events (for example, bed return, out of bed, restless, no turning) immediately after occurrence.
• Status API: Updates every 30 seconds with the latest known status and its timestamp.
• Format: JSON

Delivery method:

• HTTP POST to your endpoint (you just provide a URL)
• Or, optional delivery to your AWS S3, Azure Blob, or SFTP storage
• Security: Includes token-based auth, IP whitelisting, and optional OAuth.

2. Raw Signal File API (.CSV and .EDF)

For advanced use (e.g. signal processing, research), we offer raw sensor signal files.

Files contain:

• .CSV: Pre-processed bands (e.g. HR 6–16 Hz, RR 0.1–3 Hz)
• .EDF: Unfiltered raw data (e.g. 1–35 Hz, 0.1–3 Hz)
• Size: Typically 15–25 MB per file

Retrieval method:

• Emfit sends your system a notification with file metadata (period, link)
• Your system uses a secure API call to download the files
• Security: Partner key-based header auth

3. Direct Cloud Storage Option (Preferred for Automation)

Instead of pulling or pushing to HTTP endpoints, we can write files directly to your:

1. AWS S3
2. Azure Blob Storage
3. SFTP server

This method supports:

1. Sleep summaries (.json)
2. Raw signal files (.csv, .edf)
3. Optional compression (.gz) and AES256 encryption