Apps & scoped keys
Keep projects isolated with app-specific tenants, expiring credentials, least-privilege scopes and explicit revocation.
Medtimes DevelopersBuild healthcare
Build healthcare
into your product.
Create an app, issue a scoped sandbox key, connect webhooks and test the complete patient-to-clinician workflow on Medtimes clinical infrastructure.
Self-service sandbox · Synthetic data only · Controlled live access by approval
Medtimes Clinical API
One care backend. Multiple experiences.
01 / Your application
Register a consented patient and request care
Register a consented patient and request care
02 / Medtimes
Clinical operations coordinate clinician-led care
Clinical operations coordinate clinician-led care
03 / Your application
Receive status, signed outcomes and webhook events
Receive status, signed outcomes and webhook events
POST /api/v1/partner/consultations Authorization: Bearer mt_test_…
Everything needed to integrate safely.
Webhooks & logs
Receive signed clinical events and inspect metadata-only request logs without storing patient payloads in observability.
Controlled live access
Develop entirely in sandbox, then submit your use case, expected usage and data-handling approach for Medtimes review.
One ecosystem
External developers and Medtimes products use the same boundary.
Medtimes Health, Doorstep Health and UR Safety integrate as first-party applications through the same auditable API layer. They do not receive direct cross-database access.
Clinical authority stays with Medtimes
Developer applications control their user experience and integration. Medtimes retains authority over clinician verification, clinical decisions, signed records and live-care activation.
Claims, embedded rooms, prescribing and diagnostics adapters remain disabled until separately implemented and approved.