# Drive Health

> Guides and API reference for integrating with Drive Health.

- [Drive Health API](https://docs.drivehealth.ai/index.md): Start chat and voice conversations from your server and read what they produce.
- [Quickstart](https://docs.drivehealth.ai/quickstart.md): Set your environment and confirm your organization API key with a first request.
- [Authentication](https://docs.drivehealth.ai/authentication.md): Authenticate server requests with an organization API key.
- [Chat](https://docs.drivehealth.ai/chat.md): Start a chat with a caregiver, exchange messages, and end the session.
- [Voice calls](https://docs.drivehealth.ai/voice.md): Start phone calls from an owned number and register browser voice calls.
- [Results and recordings](https://docs.drivehealth.ai/results.md): Read the calls, chat sessions, transcripts, and recordings your organization owns.
- [API reference](https://docs.drivehealth.ai/api-reference/overview.md): Endpoints, mounts, response envelopes, pagination, and status codes.
- [Create a chat session](https://docs.drivehealth.ai/api-reference/chat/create-a-chat-session.md): Start a chat with a caregiver. The caregiver must belong to your organization. The session it creates is owned by that same organization and appears in the chat results.
- [Send a message](https://docs.drivehealth.ai/api-reference/chat/send-a-message.md): Send a message to a chat session and wait for the caregiver's reply.
- [Stream a reply](https://docs.drivehealth.ai/api-reference/chat/stream-a-reply.md): Send a message and receive the caregiver's reply as server-sent events, one JSON object per `data:` frame. The credential and the chat's ownership are checked before the stream opens, so a refused request gets an ordinary error response rather than a stream. Once the stream is open, only model failu…
- [Read a chat session](https://docs.drivehealth.ai/api-reference/chat/read-a-chat-session.md): Read one chat session and its message history.
- [End a chat session](https://docs.drivehealth.ai/api-reference/chat/end-a-chat-session.md): End a chat session. Ending marks the session; it does not erase it, and the transcript stays readable.
- [Start an outbound call](https://docs.drivehealth.ai/api-reference/voice/start-an-outbound-call.md): Start a phone call from a number your organization owns. The caregiver attached to that number runs the call. Use the returned `call_id` to read the result rather than guessing which row in the call list is yours. The call runs only when workspace balance, caregiver readiness, and the concurrency li…
- [Register a web call](https://docs.drivehealth.ai/api-reference/voice/register-a-web-call.md): Register a browser voice call and receive a LiveKit token for it. The token joins the LiveKit room for that call and nothing else. Call this from your backend and return only the token and `call_id` to the browser, never the organization API key. The call runs only when workspace balance, caregiver…
- [List calls](https://docs.drivehealth.ai/api-reference/results/list-calls.md): List calls owned by your organization. Filters narrow the list within your organization; they cannot reach past it.
- [Get a call](https://docs.drivehealth.ai/api-reference/results/get-a-call.md): Read one call your organization owns.
- [List chat sessions](https://docs.drivehealth.ai/api-reference/results/list-chat-sessions.md): List chat sessions owned by your organization. Filters narrow the list within your organization; they cannot reach past it.
- [Get a chat result](https://docs.drivehealth.ai/api-reference/results/get-a-chat-result.md): Read one chat session your organization owns, with its stored transcript.
- [Download a recording](https://docs.drivehealth.ai/api-reference/results/download-a-recording.md): Download the recording of a call your organization owns. The `call_recording_url` on a call record already points here, on the current API host. The response is the audio itself: `audio/ogg` for recordings Drive Health stored and `audio/wav` for recordings fetched from the telephony provider, so rea…

## OpenAPI Specs

- [backend](/openapi/backend.json)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.