x.com and twitter.com /status/ URLs work. The video must be under 2 minutes — X tweets are AI-transcribed, so this endpoint is slower than the others.
Request
Response
transcript is a plain string with newlines between spoken lines — there is no per-line timing in the X response and no videoUrls field.
Supported URL formats
| Format | Example |
|---|---|
x.com status | https://x.com/{user}/status/{id} |
twitter.com status | https://twitter.com/{user}/status/{id} |
x.com and legacy twitter.com domains are accepted as long as the URL points at a /status/{id} tweet. URLs without a /status/ path are rejected with 400 Invalid URL.
FAQ
Do both x.com and twitter.com URLs work?
Do both x.com and twitter.com URLs work?
Yes. Both the
x.com and the legacy twitter.com /status/ URLs are accepted.Is there a length limit?
Is there a length limit?
Yes — the video must be under 2 minutes. Longer videos can’t be transcribed by this endpoint.
Why is this endpoint slower than the others?
Why is this endpoint slower than the others?
X tweets don’t ship with captions, so the video is AI-transcribed on demand. That takes longer than the caption-based endpoints — expect a longer round trip, especially near the 2-minute limit.
Does every tweet work?
Does every tweet work?
Only tweets that contain a video. Text, image, and link tweets have nothing to transcribe and are rejected.
Does the response include timestamps?
Does the response include timestamps?
No. X transcripts are returned as plain text with newlines between lines — there is no per-line timing.