Skip to main content
Shared-chat access exposes a sanitized, read-only transcript. The route is under the standard API base URL at /shared-chats.

Endpoint

Read a shared chat

GET /shared-chats/:id Authentication depends on the chat’s access level:
For an organization-only chat, send the signed-in user’s session with the request.

Response shape

The response contains chat metadata and messages:
Only user and assistant messages are included. Message metadata is reduced to the share-safe sources, memoryUsed, delegatedAgentIds, and imageUrls fields when present. Private usage, credit, token, tool-history, and operational metadata are not exposed.
The shared response includes at most the 200 most recent messages. When older messages are omitted, transcriptTruncated is true.

Read-only behavior

This endpoint never modifies the source chat and does not provide a send-message operation. To continue a shared conversation, create a new private chat using shared_source_chat_id on POST /chats; AutoSage seeds it from up to the 120 most recent share-safe user and assistant messages.
Public links can be opened by anyone who has the URL. Change the source chat back to private to make the shared endpoint unavailable.

Next steps

Chat sharing

Learn how privacy levels and forking work.

Chats API

Create a private fork or update access level.