---
title: "Conversations"
description: "Continue, retrieve, list, manage, and share health chats."
canonical_url: "https://scholarxiv.com/developers/docs/health-api/conversations"
markdown_url: "https://scholarxiv.com/developers/docs/health-api/conversations.md"
---

> For the complete documentation index, see [llms.txt](/llms.txt).

# Conversations
URL: /developers/docs/health-api/conversations
LLM index: /llms.txt
Description: Continue, retrieve, list, manage, and share health chats.
Related: health-api, health-api/quickstart

# Conversations

Save the `chat_id` returned by `POST /api/v1/health/chat` and include it with the next `message`. The server reloads history; do not resend the transcript or provide a system prompt. A research chat ID cannot be used for a health conversation.

## Read and manage conversations

| Action                                  | Request                                                                     |
| --------------------------------------- | --------------------------------------------------------------------------- |
| Read a health conversation              | `GET /api/v1/health/chat/{chatid}` (includes `active_run`)                  |
| Read, stream, or cancel a turn          | `GET /api/v1/runs/{run_id}`, `/stream`, `POST /api/v1/runs/{run_id}/cancel` |
| List a conversation's turns             | `GET /api/v1/chats/{chatid}/runs`                                           |
| List health chats                       | `GET /api/v1/chats?surface=health`                                          |
| Rename, pin, archive                    | `PATCH /api/v1/chats/{chatid}`                                              |
| Delete the chat and its health messages | `DELETE /api/v1/chats/{chatid}`                                             |
| Share                                   | `POST /api/v1/chats/{chatid}/share`                                         |

Requests use the API key owner's conversations. See [Conversations](/developers/docs/agent-api/conversations) for the shared management request fields.

## Continue on the website

Health conversations started over the API appear in the key owner's health sidebar on the website, at `https://scholarxiv.com/health/{chat_id}`, titled from their first message. Continue them there, or pass a website health chat's id as `chat_id` from your app. A turn still running when the chat is opened streams in live. See [Continue on the website](/developers/docs/agent-api/conversations#continue-on-the-website).

## Streaming

Set `stream: true` on `POST /api/v1/health/chat` for the AI SDK UI-message event stream. `X-Chat-Id` and `X-Run-Id` are available before the first token, and every event carries an id you can resume from. See [Streaming](/developers/docs/agent-api/streaming) for the event format and [Runs](/developers/docs/agent-api/runs) for background mode, resuming, `Idempotency-Key`, and the one-turn-per-conversation rule.

The MCP `health_chat` tool calls the same health service and returns a completed answer, or a background run you read with `get_agent_run`. Website and mobile clients use session `POST /api/health/chat`, which records the same runs.

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.
Docs-scoped sitemap: [/docs/sitemap.md](/docs/sitemap.md).
Well-known sitemap: [/.well-known/sitemap.md](/.well-known/sitemap.md).
