Tutorial · Node.js
How to scrape X (Twitter) transcripts with Node.js (2026)
A Node.js walkthrough for GET /v1/twitter/tweets/transcript. Copy the snippet, run it, then read the JSON.
GET /v1/twitter/tweets/transcript · 1 credit per successful request.
In this tutorial
You'll pull a X (Twitter) transcript from a public video URL and see the text you get back.
Example job: turn a public X (Twitter) video into text for search or alerts.
Step 1
Get ready
Get a Social Fetch API key and a Node.js environment ready. New accounts include 100 free credits.
API key. Create a Social Fetch account and copy an API key. New accounts include 100 free credits.
Node.js setup. Node 18+ (native fetch). Export SOCIALFETCH_API_KEY.
When you're done, SOCIALFETCH_API_KEY is set in your shell.
Step 2
Make the request
Copy the Node.js snippet, set SOCIALFETCH_API_KEY, and call GET /v1/twitter/tweets/transcript with the x-api-key header. Example: /v1/twitter/tweets/transcript?url=https%3A%2F%2Fx.com%2Fuser%2Fstatus%2F1234567890.
You should see HTTP 200 and a JSON body. Native fetch does not throw on 4xx/5xx, so check response.ok before parsing.
Step 3
Read the response
JSON with data (the transcripts) and meta (creditsCharged, requestId). Sample below is illustrative — field docs live on the endpoint page. Credits charge on completed lookups, not transport failures.
Check data.lookupStatus when present. Keep meta.requestId if a row looks wrong.
Watch out
found plus null transcript is normal, not a retry signal. Text-only tweets have nothing to transcribe. Completed lookups still charge the documented credit when transcript is null.
Step 4
You finished
Same path and credits in playground, docs, and production. Pick a next step below.
FAQ
Common questions
Do I need an official X (Twitter) developer account?
No. Social Fetch authenticates with your Social Fetch API key. You call GET /v1/twitter/tweets/transcript and we handle upstream access. You still need to follow each platform's terms for how you use public data.
What does the x (twitter) transcripts endpoint return?
A JSON envelope with data (the transcripts) and meta (creditsCharged, requestId). Shape details and field docs live on the endpoint page and in the OpenAPI docs.
Does a found X tweet transcript lookup always return spoken text?
No. found means the tweet resolved. data.transcript can still be null when speech is not detected, the video exceeds supported length, or transcription is otherwise unavailable. A completed successful request still charges the documented credit.
Do x.com and twitter.com status URLs both work?
Yes. Pass either host as the url query param for /status/… permalinks. Branch on lookupStatus, then read data.transcript.plainText when present.
How much does a successful request cost?
1 credit per successful request.
Is this okay for production?
Yes — same production API as everywhere else: typed errors, requestId on every response, credits charged only on completed lookups. New accounts get 100 free credits.
Any Node.js-specific tips for this request?
Yes. Native fetch does not throw on 4xx/5xx — check response.ok (or status) before parsing JSON. Read meta.requestId from the body when you need support on a bad row.
Related