X / Twitter Tweet transcript API
Extract the spoken transcript from a Twitter/X video tweet by URL.
$1.20/1k req, pay per request, no subscription.
Post
buildwithjonah
@buildwithjonah
Transcript
Alright so I spent the last six months building a data pipeline that normalizes about forty different scraper APIs into one schema. I want to walk through what broke and what I would do differently if I started over today. The first lesson was that every provider's error format is completely different. Some return a 200 with an error field buried three levels deep, some return a real HTTP error code, and some just silently return an empty array. We ended up writing a translation layer just so our retry logic actually knew whether a failure meant retry later or never retry at all. The second lesson was around pagination. Cursors are never portable across providers, so we had to build our own cursor abstraction just to keep the client code simple and predictable.
{"transcript":Â "Alright so I spent the last six months building a data pipeline that normalizes about forty different scraper APIs into one schema. I want to walk through what broke and what I would do differently if I started over today. The first lesson was that every provider's error format is completely different. Some return a 200 with an error field buried three levels deep, some return a real HTTP error code, and some just silently return an empty array. We ended up writing a translation layer just so our retry logic actually knew whether a failure meant retry later or never retry at all. The second lesson was around pagination. Cursors are never portable across providers, so we had to build our own cursor abstraction just to keep the client code simple and predictable."}
Pricing and providers
X / Twitter Tweet transcript API pricing: one API, 2 interchangeable providers
The cheapest provider serves first. If it fails, the next one takes over in the same call.
Call it
Get X / Twitter tweet transcript in one request
import os, requests res = requests.post( "https://api.getanyapi.com/v1/run/twitter.tweet_transcript", headers={"Authorization": f"Bearer {os.environ['ANYAPI_KEY']}"}, json={ "url": "" }, ) print(res.json())
{
"found": true,
"data": {
"transcript": "Alright so I spent the last six months building a data pipeline that normalizes about forty different scraper APIs into one schema. I want to walk through what broke and what I would do differently if I started over today. The first lesson was that every provider's error format is completely different. Some return a 200 with an error field buried three levels deep, some return a real HTTP error code, and some just silently return an empty array. We ended up writing a translation layer just so our retry logic actually knew whether a failure meant retry later or never retry at all. The second lesson was around pagination. Cursors are never portable across providers, so we had to build our own cursor abstraction just to keep the client code simple and predictable."
}
}Full parameter and response reference - every field, type, and example for this endpoint.
Reference
One request, one response shape.
Every field you send and every field you get back, each with a real example.
Last verified 2026-10-06 · uptime and latency measured over 30d
Request body
JSON, posted to this endpoint.
- urlstring
https://x.com/buildwithjonah/status/1842093771280384512
Tweet URL of the video to transcribe (e.g. https://x.com/TheoVon/status/1916982720317821050).
Response
JSON, one example value per field.
- foundboolean
true
- transcriptstring
Alright so I spent the last six months building a data pipeline that normalizes about forty different scraper APIs into one schema. I want to walk through what broke and what I would do differently if I started over today. The first lesson was that every provider's error format is completely different. Some return a 200 with an error field buried three levels deep, some return a real HTTP error code, and some just silently return an empty array. We ended up writing a translation layer just so our retry logic actually knew whether a failure meant retry later or never retry at all. The second lesson was around pagination. Cursors are never portable across providers, so we had to build our own cursor abstraction just to keep the client code simple and predictable.
FAQ
About the X / Twitter Tweet transcript API
The AnyAPI X / Twitter Tweet transcript API returns X / Twitter tweet transcript data as normalized JSON from one POST call to /v1/run/twitter.tweet_transcript. Extract the spoken transcript from a Twitter/X video tweet by URL. AnyAPI routes each request across 2 sources and falls back automatically when one fails. It costs from $1.20 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of X / Twitter tweet transcript calls through AnyAPI succeeded, with a median response time of 3.4 seconds across 19 measured calls.