Ion
Ion•3w ago

Get Transcript Dialog API

Regarding the Get Transcript Dialog API since it is Deprecated what can I use instead to get the transcripts dialog im confused
4 Replies
Tico | Voiceflow Assistant
Tico | Voiceflow Assistant•3w ago
Hey there! 👋
The “Get Transcript Dialog” endpoint that lives at GET /transcripts/{projectID}/{transcriptID} is part of the Transcripts API.
​ • It is considered a legacy-view endpoint, but it has not been removed or shut-off – Voiceflow has no current deprecation timeline for those routes (see the note in our “Better Transcripts” launch blog).
• If you’re building something new you can keep using this same Transcripts API family, or start with the newer list endpoint: GET /transcripts/{projectID} ➜ returns the list of transcripts for a project. ​ Typical flow
1️⃣ List the transcripts you care about
GET /transcripts/{projectID}?tag=…&range=…
2️⃣ Pull the full turn-by-turn dialog for one transcript
GET /transcripts/{projectID}/{transcriptID}?limit=100&offset=0
3️⃣ (optional) Export as CSV
GET /transcripts/{projectID}/{transcriptID}/export?format=csv ​ If you’re saving conversations yourself (e.g. through a custom DM deployment) make sure you’re creating transcripts first with the PUT /transcripts endpoint, then read them as above. ​ So in short: keep using the Transcripts API — the “Get Transcript Dialog” route is still the correct one to fetch the messages inside a saved transcript.
Docs: https://developer.voiceflow.com/reference/fetchtranscripts
Hope that clears it up!
Ion
IonOP•3w ago
Why is it in the docs Ive inserted the project id transcript id and api as a header and I was met with a error?
Tico | Voiceflow Assistant
Tico | Voiceflow Assistant•3w ago
Here are the most common reasons a /transcripts request fails even though you’ve supplied the projectID, transcriptID and an Authorization header: 1. Using the wrong API key
 • The Project API only accepts the project DM API key that you’ll find in Project › Integrations › API Key (it starts with VF.DM.).
• Personal access-tokens or keys from another project will return 401 | Unauthorized. 2. Extra / missing text in the header
 • Send the key exactly as-is →
Authorization: VF.DM.xxxxxxxxxxxxxxxxx…
• Don’t prefix it with Bearer or wrap it in quotes. 3. Wrong endpoint format
 • Retrieve a single dialog with:
GET https://api.voiceflow.com/v2/transcripts/{projectID}/{transcriptID}
• Make sure the IDs in the path match the key’s project. 4. Passing unrelated headers
 • versionID, Content-Type, etc. aren’t needed for this GET call and can sometimes confuse API gateways.
• Keep it to only the Authorization header unless you’re adding optional query params (limit, offset, dates …). Example working call 
curl --request GET \
  --url https://api.voiceflow.com/v2/transcripts/63204daf2c4a550006873772/63204daf2c4a550006873773 \
  --header "Authorization: VF.DM.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
curl --request GET \
  --url https://api.voiceflow.com/v2/transcripts/63204daf2c4a550006873772/63204daf2c4a550006873773 \
  --header "Authorization: VF.DM.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
If you still see an error after checking the four items above, note the exact status code: • 401 → wrong / expired key • 404 → transcriptID doesn’t exist for that project or typo in IDs • 403 → key belongs to a different project Docs reference: https://docs.voiceflow.com/reference/project-api-transcripts
Ion
IonOP•3w ago
I inserted the correct credentials and was met with { "code": 500, "status": "Internal Server Error", "dateTime": "2025-08-09T15:11:12.759Z", "timestamp": 1754752272759, "data": "not found" }

Did you find this page helpful?