Skip to main content
Chat share routes let a signed-in user publish or revoke read-only views of a conversation, similar to ChatGPT’s shareable links. Authenticated routes live under /api/v1/share, while anonymous consumers access /api/v1/public/share.

Quick facts

  • Authenticated calls require an Auth0 Bearer token
  • Share IDs are short, URL-safe identifiers generated via nanoid
  • Public viewers are fingerprinted via IP + User-Agent to track viewCount and enforce continuation limits
  • Expiration defaults to “never” but can be overridden per share (1–365 days)
Check each endpoint page for request/response schemas, example payloads, and the interactive OpenAPI console.