Feedback
Roadmap
Changelog

Help make Supadata better.

Tell us how we could make the product more useful to you.

Need help? Use the chat button in the corner to contact us.

Subject: availableLangs field only returns the requested language instead of all available subtitles

Hi Supadata Team, I've been using your Transcript API and noticed an issue with the availableLangs field in the response. Issue Description When I request a YouTube video transcript with mode=auto or a specific lang parameter, the availableLangs field in the response only contains the language that was returned, not all the subtitle languages available on YouTube. Expected Behavior The availableLangs field should return all available subtitle languages for the video, regardless of which language was requested. This would allow users to: Know what languages are available before making a request Let users manually select a different language if their preferred one isn't available Actual Behavior // Request: GET /v1/transcript?url=...&mode=auto&lang=ko // Response: { "lang": "zh", "availableLangs": ["zh"], // ❌ Only shows "zh", but video has ko, en, ja, etc. "content": [...] } Even though the YouTube video has multiple subtitle languages (Korean, English, Japanese, etc.), the API only returns ["zh"] in availableLangs. Steps to Reproduce Find a YouTube video with multiple subtitle languages Call the API with mode=auto or any specific lang Check the availableLangs field - it only contains the returned language Suggested Fix Please return all available subtitle languages from YouTube in the availableLangs field, not just the one that was returned. This is critical for applications that need to offer language selection to users. Example of Expected Response { "lang": "zh", "availableLangs": ["ko", "en", "zh", "ja", "es"], // ✅ All available languages "content": [...] } Thank you for looking into this! Best regards, Steve

tcytcy111 2 days ago

Missing createdAt field in metadata endpoint response

Hi Supadata team, I'm using the /v1/metadata endpoint to fetch YouTube video metadata, and I've noticed that the createdAt field is no longer being returned in the response. Expected behavior (per documentation): The response should include a createdAt field with the publication timestamp in ISO 8601 format. Actual behavior: The response contains platform, type, id, url, title, description, author, stats, media, tags, and additionalData — but no createdAt field. Example request: GET https://api.supadata.ai/v1/metadata?url=https://www.youtube.com/watch?v=SnLBOQvJhaY Example additionalData returned: {"channelId": "UCM3vJxmuJJkk1r0yzFI9eZg", "transcriptLanguages": ["pt"]} This was working correctly until recently (around January 28-29, 2026). Videos fetched before that date have the publish date populated. Could you look into this? The createdAt field is essential for my application to filter videos by publication date. Thanks,

leo.majowka 5 days ago

Completed

Successful response but Empty Content youtube transcript API

Example: issue on this video https://www.youtube.com/watch?v=m-M_HzS4w2Q Here you have a successful response from the API but PROBLEM: empty array is returned in “content: []”, no transcript although a lot of languages shown are available !"show transcript" and all languages captions are available on youtube, can you estimate the time it will take to fix all problems ? Thank you for your time and patience

Alexandre 7 days ago

2

Completed

Problem with transcript API

Let’s take this video (french podcast) https://www.youtube.com/watch?v=TJ2vvygql48 When asking for “native” caption in “Auto“ it works well dans say —> that “en“ lang is available, but when asking for “en“ then it doesn’t work. Another information is that the doc says when preferred language is not available it takes the default one, which is not the case. https://docs.supadata.ai/get-transcript?_gl=1*1u7qxxi*_gcl_au*MTc1MTE5ODAyNC4xNzY5MjY3MjI5LjE3MDE2NTAxNzkuMTc2OTI2NzI1OC4xNzY5MjY3NDcz#languages You can try it in the playground, or using code, same result.

Alexandre 7 days ago

2

Intermittent empty transcriptLanguages in /v1/metadata for YouTube

The `transcriptLanguages` field in the `/v1/metadata` endpoint is returning intermittent results for YouTube URLs (e.g., https://www.youtube.com/watch?v=L5anUhwF9dc). Sometimes it returns the correct languages (e.g., `["es"]`), and other times it returns an empty array `[]` for the same video. This is affecting production workflows where the user cannot switch to deprecated endpoints. The user expects consistent detection of available transcripts.

martin 10 days ago

Rejected

Wrong Youtube Video is processed to generate transcript

I sent a generate request for https://www.youtube.com/watch?v=E-6nR51kZKE 2 times spaced a couple of hours apart. The first attempt generated the correct transcript. The second attempt generated a transcript for a different video. This is the job id: 2026-01-04 16:14:03 GET /v1/transcript/05c01409-b488-4981-b591-62dfae5d988e This has happened to me several times. The AI Support bot said it was because of a cached object and recommended i always generate rather than use AUTO. Please fix this issue as GENERATE is not reliably generating the correct transcript.

subscriptions 29 days ago

1

Planned

Distinguish manual vs auto-generated transcripts in metadata

I want a way to distinguish between manually uploaded transcripts and auto-generated ones in the metadata (specifically in the transcriptLanguages array). Currently, I have to iterate through all available languages using mode=native to find a manual one and avoid 206 errors or unwanted AI generation costs from mode=generate. It is difficult to implement this iteration when there are 50+ languages, and the first language in the list isn't always the native one. Adding a 'type' or 'isManual' flag to each language in the metadata would allow me to target the correct native transcript directly.

martin About 2 months ago

3