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.

Error 400 and depreciated YouTube video gettranscript.

I see you have now depreciated the single use GetTranscript and it is indeed failing with 400 errors on my site. https://docs.supadata.ai/api-reference/endpoint/youtube/video-get This was working fine for two months and the reason I purchased a yearly sub. Before I migrate to your batch downloading of transcripts is that depreciated too? How do you notify live production sites when you remove functionality they utilize? Please advise if this is superseded with another function. I can only find batch. Snippet: ## Documentation Index Fetch the complete documentation index at: https://docs.supadata.ai/llms.txt Use this file to discover all available pages before exploring further. # Transcript Get transcript from YouTube video in various formats and languages. If the lang parameter is not provided or the transcript is not available in the requested language, the API defaults to the first available language. ## OpenAPI ````yaml v1-openapi GET /youtube/transcript openapi: 3.1.0 info: title: Supadata description: Web & Social Media Content API for Developers version: 1.3.0 servers: - url: https://api.supadata.ai/v1 security: - apiKeyAuth: [] paths: /youtube/transcript: get: description: >- Get transcript from YouTube video in various formats and languages. -

supadata.ai 3 days ago

Bug: Metadata.__init__() missing required url argument when calling supadata_client.metadata()

When calling supadata_client.metadata(url=tiktok_url), the SDK throws a TypeError instead of returning the metadata object. I am trying to just get the video description from a tiktok. Error TypeError: Metadata.__init__() missing 1 required positional argument: 'url' Steps to Reproduce python from supadata import Supadata client = Supadata(api_key="your_api_key") metadata = client.metadata(url="https://www.tiktok.com/@user/video/123456") Expected Behaviour A Metadata object is returned containing the video metadata including description,title, author etc. Actual Behaviour The API call succeeds and returns a response, but the SDK fails to construct the Metadata object because the url field is missing from the response, causing a TypeError. Workaround Currently bypassing the SDK and calling the API directly: (python) import requests response = requests.get( "https://api.supadata.ai/v1/tiktok/metadata", params={"url": tiktok_url}, headers={"x-api-key": "your_api_key"} ) data = response.json() Environment Python version: 3.12 Supadata SDK version: 1.6.0 OS: macOS

franklatank01 7 days ago

Failed requests 5/19 to present

Title: /v1/youtube/channel/videos returns empty videoIds for all channels since ~May 19, 2026 Body: Since approximately May 19, my production app stopped receiving new videos from this endpoint. Every channel I query — including major channels with daily uploads — returns: {"videoIds":[],"shortIds":[],"liveIds":[]} Reproduced with these channels (all have many recent uploads): 20VC: https://www.youtube.com/@20VC (also tried as channel URL) MKBHD: UCBJycsmduvYEL83R_U4JriQ BBC News: UC16niRr50-MSBwiO3YDb3RA Requests return HTTP 200 with no error. The /v1/youtube/transcript endpoint works normally for direct video URLs, so it's specific to channel-videos. My API key is active and has credits. Could someone investigate? My production ingest pipeline has been silent for 48+ hours.

nick 8 days ago

Intermittent partial response from /v1/metadata for Instagram Reels: author present but media.thumbnailUrl and author.avatarUrl missing

For Instagram Reel URLs, the GET /v1/metadata endpoint intermittently returns a response that includes the author display name but omits the thumbnail and the author avatar. The same URL returns a complete response on most requests, so this appears to be a transient server-side issue rather than missing data for the post. Endpoint: GET https://api.supadata.ai/v1/metadata?url= Example URL that reproduces it: https://www.instagram.com/reel/DXzqhy6pfR-/ Reproduction and frequency: At roughly 2.5 requests/sec: ~1 in 6 requests returned the partial response. Spaced 2 seconds apart, which is within a 1 request/sec plan limit: still ~2 in 8 requests returned the partial response. Because it reproduces with 2 second spacing on a 1 req/sec plan, this is not a rate-limit effect. It is an intermittent server-side issue on the same URL. Expected response (majority of requests): author.displayName present author.avatarUrl present media.thumbnailUrl present Actual response (intermittent, ~20 to 25% of requests for the same URL): author.displayName present author.avatarUrl missing or empty media.thumbnailUrl missing or empty Questions: Under what conditions can /v1/metadata return author.displayName without media.thumbnailUrl / author.avatarUrl for a post that does have them? Is there a field or status in the response we should check to detect an incomplete result, rather than treating any 200 as complete? Is there a recommended retry or backoff approach, or a parameter to force a fully resolved response?

janhoff2000 10 days ago

Change in Transcript Output Format

Hi Supadata team, I've been using youtube transcript API for a while and recently noticed a change in the format of the output that is breaking my application. Previously, when fetching a transcript, the content was returned as clean, structured text where each speaker's speech was grouped into a complete sentence or paragraph. This made it easy to process and identify speaker turns. However, sometime around January 17, 2026, the output format changed. The transcript is now returned as a sequence of short fragmented chunks — exactly as the captions appear on YouTube (short timed snippets). This makes it very difficult to work with programmatically, as the text is broken mid-sentence and speaker turns are no longer clearly grouped. Here is a simplified example of what I was getting before: Speaker 1 sentence here, complete and readable. Speaker 2 response here, also complete. And here is what I get now: word word word word word word word word word I haven't made any changes to my API request. I'm using the following parameters: mode: auto lang: ar I have two transcripts generated on the same day (2026-01-17) where the first one has the old format and the second already has the new format, which suggests the change happened on your side on that date. Could you please clarify: Was there an intentional change to the output format around that date? Is there a parameter I can use to get back the old structured format? If this was a breaking change, will it be documented going forward? Thank you for your time and I look forward to your response.

contact.galdi about 2 months ago