Skip to main content
GET
/
api
/
v1
/
user
/
conversations
/
{conversationId}
Get conversation details
curl --request GET \
  --url https://handauncle-backend-prod-205012263523.asia-south1.run.app/api/v1/user/conversations/{conversationId} \
  --header 'Authorization: Bearer <token>'
{
  "data": {
    "id": "<string>",
    "lastMessageAt": "2023-11-07T05:31:56Z",
    "messageCount": 123,
    "userId": "<string>",
    "createdAt": "2023-11-07T05:31:56Z",
    "title": "<string>",
    "prepromptKey": "<string>",
    "preview": "<string>",
    "pinned": true,
    "tags": [
      "<string>"
    ],
    "metadata": {
      "firstMessage": "<string>",
      "tags": [
        "<string>"
      ],
      "pinned": true,
      "model": "<string>"
    }
  },
  "meta": {
    "timestamp": "2023-11-07T05:31:56Z",
    "requestId": "<string>"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.handauncle.com/llms.txt

Use this file to discover all available pages before exploring further.

Fetches a single conversation with metadata (status, counts, tags, pinned state, and timestamps). Useful when the UI opens a chat and needs to confirm ownership or show enriched metadata alongside message history.

​
Response Metadata

The response includes all conversation metadata:
  • type: 'chat' or 'second_opinion' - Conversation type
  • inputType: 'text', 'file', or 'voice' - How the conversation was initiated
  • prepromptKey: The pre-prompt used when creating this conversation (if any)
  • userId: The owner of the conversation
  • createdAt: When the conversation was created
  • lastMessageAt: Timestamp of the last message
  • messageCount: Total number of messages
  • status: Current status (active, archived, or deleted)
  • metadata: Additional metadata including tags, pinned state, and model

​
Authentication

Supports both authentication methods:
  • Auth0 JWT: Authorization: Bearer <token> (registered users)
  • Device-based: x-device-id, x-user-id, x-platform headers (guest users)
In the playground above, select your preferred authentication method from the security dropdown.

Authorizations

​
Authorization
string
header
required

Auth0 access token for registered users.

Path Parameters

​
conversationId
string
required

Conversation ID (MongoDB ObjectId).

Required string length: 24

Response

Conversation returned.

​
success
enum<boolean>
required
Available options:
true
​
data
object
required
​
meta
object
required