MyMojoHealth is the cloud platform for Keto-Mojo blood glucose and ketone meters. Adding it would give Open Wearables coverage of intermittent fingerstick blood-glucose data (vs the continuous CGM data already covered by Ultrahuman / pending Dexcom #298), plus blood ketones — which no current provider exposes.
Integration FAQ
Is the integration free and self-enrollment?
Partial. There's a Limited API Partner program with instant self-registration via https://auth.us.mymojohealth.com/partner/register. Free initial tier capped at 10 user connections per partner account; higher limits require approval. Regional accounts (US, EU, CA — multi-region cloud).
Is there a sandbox? Do I need a physical device?
No dedicated sandbox is documented, and the data flow assumes a physical Keto-Mojo meter syncing to a real user's MyMojoHealth account. Each user explicitly consents to share their data with the third-party platform (OAuth-style consent). For dev, looks like we'd need at least one real meter + test account.
What data is exposed?
- Blood glucose readings (fingerstick, intermittent — typically a few per day)
- Blood ketones (β-hydroxybutyrate)
- GKI (Glucose Ketone Index) — derived metric
Auth, base URL, rate limits, webhooks?
- Auth method not explicitly stated on the public marketing page; details are in the partner-only Swagger docs and GitHub-hosted public docs.
- Base URLs are regional (
api.us.mymojohealth.com, plus EU/CA equivalents).
- No rate limits or webhook/push support are publicly documented — likely poll-based (similar to early Polar/Withings).
- HIPAA / PIPEDA / GDPR compliance is mentioned.
How would it fit Open Wearables?
Series types blood_glucose and insulin_delivery already exist in enums/series_types.py and have webhook event types defined. Ketones and GKI would need new series types. Provider strategy would slot in alongside Whoop / Oura / Withings — capabilities rest_pull=True, webhook_callback=False (until they ship webhooks).
Additional context
MyMojoHealth is the cloud platform for Keto-Mojo blood glucose and ketone meters. Adding it would give Open Wearables coverage of intermittent fingerstick blood-glucose data (vs the continuous CGM data already covered by Ultrahuman / pending Dexcom #298), plus blood ketones — which no current provider exposes.
Integration FAQ
Is the integration free and self-enrollment?
Partial. There's a Limited API Partner program with instant self-registration via
https://auth.us.mymojohealth.com/partner/register. Free initial tier capped at 10 user connections per partner account; higher limits require approval. Regional accounts (US, EU, CA — multi-region cloud).Is there a sandbox? Do I need a physical device?
No dedicated sandbox is documented, and the data flow assumes a physical Keto-Mojo meter syncing to a real user's MyMojoHealth account. Each user explicitly consents to share their data with the third-party platform (OAuth-style consent). For dev, looks like we'd need at least one real meter + test account.
What data is exposed?
Auth, base URL, rate limits, webhooks?
api.us.mymojohealth.com, plus EU/CA equivalents).How would it fit Open Wearables?
Series types
blood_glucoseandinsulin_deliveryalready exist inenums/series_types.pyand have webhook event types defined. Ketones and GKI would need new series types. Provider strategy would slot in alongside Whoop / Oura / Withings — capabilitiesrest_pull=True,webhook_callback=False(until they ship webhooks).Additional context