Tutorial · curl
How to scrape X (Twitter) search results with curl (2026)
A curl walkthrough for GET /v1/twitter/search. Copy the snippet, run it, then read the JSON.
GET /v1/twitter/search · 2 credits per successful request.
In this tutorial
You'll search X (Twitter) for a phrase and see the results you get back.
Example job: find X (Twitter) results for a phrase, then open the URLs you keep.
Step 1
Get ready
Get a Social Fetch API key and a curl 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.
curl setup. Any shell with curl. Export SOCIALFETCH_API_KEY before you run the sample.
When you're done, SOCIALFETCH_API_KEY is set in your shell.
Step 2
Make the request
Copy the curl snippet, set SOCIALFETCH_API_KEY, and call GET /v1/twitter/search with the x-api-key header. Example: /v1/twitter/search?query=product+launch.
You should see a JSON body on stdout. Use curl -sS so HTTP errors still print on stderr.
Step 3
Read the response
JSON with data (the search results) 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
bill from meta.creditsCharged — X search isn't the flat 1-credit assumption. Keep section, minLikes, and filters stable when advancing cursor.
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/search 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) search endpoint return?
A JSON envelope with data (the search results) and meta (creditsCharged, requestId). Shape details and field docs live on the endpoint page and in the OpenAPI docs.
When should I use section=latest vs section=top on X search?
Use latest for crisis watches and frequent polls where recency matters. Use top for recap-style dashboards. Other section values include people, photos, and videos. Omit section to use the default top feed. Keep section and other filters stable across cursor pages.
Why does X search cost more than TikTok or YouTube search?
This operation is priced higher in the registry than most platform search routes. Always read meta.creditsCharged on the response — do not hard-code a 1-credit assumption from another platform's search tutorial.
How much does a successful request cost?
2 credits 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 curl-specific tips for this request?
Yes. Pass the key with -H "x-api-key: $SOCIALFETCH_API_KEY", and wrap the full URL in double quotes so the shell does not split on & in query strings. Prefer curl -sS so HTTP errors still surface on stderr.
Related