GET Endpoints — No Proxy or Cookies Needed
Read-only endpoints support GET requests that use a server-side pool of cookies and proxies. You only need your X-API-Key header:
curl "https://api.apitwitter.com/twitter/user/elonmusk" \
-H "X-API-Key: tda_your_key"
Supported GET endpoints include: user lookups (by username, ID, batch), followers, following, replies, mutual followers, user tweets, tweet lookups, and search.
Proxy — Required for POST
We do not provide proxies. Every POST request must include your own proxy URL. POST requests without a proxy receive a 400 Bad Request response.
How to Pass Proxy
POST endpoints use a JSON body. Include "proxy" as a field in the request body:
{
"cookie": "ct0=...;auth_token=...",
"proxy": "http://user:pass@host:port"
}
http://user:pass@host:port
socks5://user:pass@host:port
http://host:port
Recommended Proxy Types
| Type | Best For | Quality |
|---|
| Residential | All operations | Best |
| ISP / Static | High-volume reads | Good |
| Datacenter | Testing only | Fair |
For best results, use high-quality residential proxies and rotate them across requests.
Cookies — Required for POST
We do not provide cookies. Every POST request must include your own Twitter session cookies. We never store your cookies. GET endpoints handle this server-side.
How to Pass Cookies
POST endpoints use a JSON body. Include "cookie" as a field in the request body:
{
"cookie": "ct0=YOUR_CT0;auth_token=YOUR_AUTH_TOKEN",
"proxy": "http://user:pass@host:port"
}
A raw cookie string with semicolon-separated key=value pairs.
Required keys: ct0 and auth_token
ct0=YOUR_CT0_VALUE;auth_token=YOUR_AUTH_TOKEN
How to Get Your Cookies
Log in to X.com
Open x.com in your browser and log in to your Twitter account. Open Developer Tools
Press F12 (or right-click → Inspect). Go to the Application tab.
Navigate to Cookies
In the left sidebar: Cookies → https://x.com
Copy Values
Find and copy the values of ct0 and auth_token.
Format the String
Combine them: ct0=YOUR_CT0;auth_token=YOUR_AUTH_TOKEN
Verifying Your Cookies
Use the session verify endpoint to check if your cookies are valid:
curl -X POST "https://api.apitwitter.com/twitter/session/verify" \
-H "X-API-Key: tda_your_key" \
-H "Content-Type: application/json" \
-d '{"cookie": "ct0=abc123;auth_token=xyz", "proxy": "http://user:pass@proxy:8080"}'
This returns the username associated with the cookies, costing only 5 credits.