Skip to main content

Overview

Sevah platform · API v1

Sevah connects clinical operators, care workflows, and companion devices through one tenant-scoped control plane. Use the API to authenticate devices, coordinate rounds, manage care operations, and route realtime voice sessions without weakening the boundaries around protected health information.

Check the service
curl https://app.sevah.ai/health

Platform capabilities​

Each capability is available through a focused API surface and shares the same organization, audit, and runtime validation model.

IdentityTenant-scoped care operationsSession-backed access for facilities, rooms, patients, care plans, conversations, and staff.DevicesCompanion control planeAuthenticate hardware, pair it to a room, receive commands, and stream round audio.WorkflowsMissions and roundsDeliver structured work to devices and preserve the outcome as an auditable care event.RealtimeVoice and conversation recordsRoute provider-backed voice sessions and archive the minimum operational record required.

How Sevah works​

1. Establish identity​

Human operators exchange Firebase identity for a secure Sevah session. Devices exchange their canonical hardware identifier for a short-lived bearer token. Every protected request is resolved to one organization before application data is read.

2. Validate the runtime​

The service validates configuration before accepting traffic. Secure deployments refuse to boot when signing secrets, admin controls, provider credentials, or PHI-egress interlocks are incomplete.

3. Coordinate care work​

The control plane publishes missions and round triggers, routes realtime media, records outcomes, and exposes those records to authorized operators in the clinical console.

Built for production​

Fail-fast configurationBoot and readiness checks prevent partially configured secure deployments from serving traffic.
Explicit tenant boundariesOrganization context is required by protected chart and operational routes.
Auditable PHI accessClinical reads, writes, exports, and break-glass operations are designed to leave an audit trail.
OpenAPI-first contractThe interactive reference is generated from the same specification validated in CI.

Get started​

Docker quickstart →Build, validate, and run the API with the repository's pinned workflow.Explore the API →Browse schemas, authentication requirements, and request examples.