Sonde Health API Platform Documentation
Getting Started - Choose Sonde Cloud API, Sonde Edge SDK, or Sonde Edge Passive SDK
- Mohdsiddique Bagwan (Unlicensed)
- Aman Jain
- Nikhil Jagshettiwar
Sonde offers vocal biomarkers integration in your application through Sonde Cloud API, Sonde Edge SDK, and Sonde Edge Passive SDK. Sonde Edge and Passive SDK allow partners to integrate their applications on the edge devices such as mobile phones and smart speakers.
Â
Choosing Sonde Cloud API or Sonde Edge API:
The following are some tradeoffs for you to select between multiple options.
 | Sonde Cloud API | Sonde Edge Cued SDK | Sonde Edge Passive SDK |
|---|---|---|---|
Definition | Your application will capture the audio on the device and send it via API calls to the Cloud. Here the score will be calculated and through an API call you will receive the score. | Your user will be cued (asked a question or an activity to elicit a voice response). Your application will capture the audio on the device. The audio will remain on the device and score will be calculated on the device. This offers high security and privacy as well as low latency and no internet access. | Your user voice will be passively analyzed in the background. Your application will continuously analyze the audio in background and only filters the authorized user voice and rejects the other user voices. The audio will remain on the device and the score will be calculated on the device. This offers high security and privacy as well as low latency and no internet access. |
OS support | Mobile phones with Android and iOS that have audio capture capability. | Support for both Android and iOS. | Support for both Android and iOS. |
Health check support (refer to documentation for more details) | Respiratory | Respiratory | Mental Fitness |
Network connectivity | Medium to strong connectivity preferred. Application will still work in slow connectivity but scores return may take up to 30 seconds. | Application can execute with no network connectivity. However, for the purposes of registration and metering some connectivity is recommended. | Application can execute with no network connectivity. However, for the purposes of registration and metering some connectivity is recommended. |
Latency | 12-30 seconds based on the network connectivity and length of audio captured. | 2-4 seconds based on Edge device speed and length of audio captured. | 2-4 seconds based on Edge device speed and length of audio captured. |
Data Transfer | Real-time audio uploaded to generate the scores. 600 KB for Respiratory audio uploaded (6 seconds of ‘Ahh’); | For billing and building personalized models, usage metering and meta-data is uploaded to the backend. Data includes scores, date/time stamp, users YOB, gender scores, and device OS and model. | Optionally scores, and device specific meta-data may be uploaded to the Cloud. |
Security and Privacy | All audio/data transfer to the cloud is on HTTPS. | Captured audio for scoring is not stored on the device. App developers need to delete the audio after getting scores. | Analyzed audio for scoring is not stored on the device. |
Integration effort (not including UI/UX) | 1-3 days | 1-3 days | 3-5 days |
Upgrades and bug fixes | Higher flexibility as this does not require changes in your Edge app build. | SDK upgrades will require app upgrades. | SDK upgrades will require app upgrades. |
Access to API/SDK | Contact Sonde | Contact Sonde | Contact Sonde |
Cost | Contact Sonde | Contact Sonde | Contact Sonde |
For additional information, please contact support@sondehealth.com.
Â
Â
Sonde Health