---
title: "Conversations"
description: "Read, list, rename, pin, archive, delete and share the conversations the agent stores for an API key."
canonical_url: "https://scholarxiv.com/developers/docs/agent-api/conversations"
markdown_url: "https://scholarxiv.com/developers/docs/agent-api/conversations.md"
---

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

# Conversations
URL: /developers/docs/agent-api/conversations
LLM index: /llms.txt
Description: Read, list, rename, pin, archive, delete and share the conversations the agent stores for an API key.
Related: agent-api, agent-api/quickstart, agent-api/files

# Conversations

Every turn is stored under the `chat_id` returned by `POST /api/v1/chat`. These routes read and manage that history.

## Read a conversation

```bash
curl https://scholarxiv.com/api/v1/chat/65a000000000000000000001 \
  -H "Authorization: Bearer sxv_your_key_here"
```

Returns `{ "chat_id": "…", "title": "…", "messages": [...] }`. Messages include persisted text, tool parts, and metadata. The same conversation can be opened in the website's chat workspace. Access to another user's chat returns 404. Health and figure conversations are excluded.

## Manage conversations

| Action | Request |
|---|---|
| List chats | `GET /api/v1/chats?surface=research` |
| Rename, pin, archive | `PATCH /api/v1/chats/{chatid}` with `title`, `pinned`, or `archived` |
| Delete | `DELETE /api/v1/chats/{chatid}`. A health conversation also deletes its stored messages. |
| Share | `POST /api/v1/chats/{chatid}/share` |

All of these use the same `sxv_` key as the agent call.

## Continuing a conversation

Send one request at a time per conversation. Execution is tied to the active request; there is no background run, resumable event log, or idempotency key. Do not automatically retry a POST after losing the connection: it may have already saved a turn or performed tools. Inspect history using the saved ID first. A fresh POST without `chat_id` always creates a new conversation.

A health conversation is read and managed through the [Health Chat API](/developers/docs/health-api).

## 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).