Integration Guide
This guide covers everything required to build a production-ready Apollo integration — patient data, recording requirements, dual upload, data deletion, and error handling. If you have not yet made your first Apollo API call, start with the Quickstart.
Apollo is a regulated medical device intended for use by qualified healthcare professionals only. It must not be used as a substitute for clinical judgement or for self-assessment.
Architecture
- Your backend — creates model runs, handles recording uploads, and polls for results via the thymia API. Your API key must never be exposed in client-side code.
- Your frontend — captures or sources two voice recordings per patient and passes them to your backend for upload.
- thymia API — processes both recordings and returns disorder scores, symptom scores, and a clinical report.
Patient data
Do not include personally identifiable information in the
userLabel field. Use an anonymised reference from your system
to ensure compliance with GDPR and HIPAA requirements.
Recordings
Recording requirements
Both upload URLs expire 1 hour after the model run is created. The model will not begin processing until both recordings have been successfully uploaded.
Uploading recordings
Data deletion
thymia is GDPR and HIPAA compliant and ISO 13485 certified. For data processing agreements or privacy queries specific to clinical deployments, contact support@thymia.ai.
Polling for results
Accessing results
Error handling
Multi-region
Next steps






