What this page used to describe (0.10.x)
Vexa could mint a public, unauthenticated, short-lived URL for a transcript:- An authenticated call created a share id; the transcript was rendered as plain text and stored under a TTL (default 15 minutes).
- The response returned a URL of the form
/public/transcripts/<share_id>.txt. - You handed that URL to ChatGPT — “Read from this URL so I can ask questions about it” — and ChatGPT fetched it directly, avoiding paste-length limits.
What is true in 0.12 today
GET /public/transcripts/{share_id}.txtis sealed in the API contract but not served by any component. A URL of that shape will not resolve on a 0.12 deployment.- A share endpoint exists under the same name —
POST /meetings/{platform}/{native_meeting_id}/share— but it does something different: it mints a token that another authenticated Vexa user redeems (POST /transcripts/share/accept). It is user-to-user sharing inside a Vexa deployment, not a public URL, and an external assistant cannot consume it.
What you can do today
To get a transcript into ChatGPT or any assistant right now:- Fetch and paste/upload: retrieve the transcript with an API key carrying the
txscope —GET /transcripts/{platform}/{native_meeting_id}— and paste or upload the text into your assistant. - Share to a teammate inside Vexa: use the 0.12 share/accept flow above (both sides authenticated).