Skip to main content

​
Prerequisites

Before making your first request, you need:
  1. An ApiTwitter account — register here
  2. Credits on your balance — minimum $10 top-up
For GET read endpoints, that’s all you need. For POST endpoints (which give you full control with your own cookies), you also need:
  1. Your Twitter cookies (ct0 and auth_token)
  2. A proxy URL

​
Step 1: Get Your API Key

After registration, your API key is automatically created. Find it in your Dashboard → API Key page. Your key looks like: tda_k8x2mN3s_...

​
Step 2: Get Your Twitter Cookies

  1. Open x.com and log in
  2. Open DevTools (F12) → Application → Cookies → https://x.com
  3. Copy the values of ct0 and auth_token
  4. Format them as: ct0=YOUR_CT0;auth_token=YOUR_AUTH_TOKEN

​
Step 3: Make Your First Request

​
Option A: GET (simplest — uses server pool)

curl "https://api.apitwitter.com/twitter/user/elonmusk" \
  -H "X-API-Key: tda_your_key_here"

​
Option B: POST (your own cookies & proxy)

curl -X POST "https://api.apitwitter.com/twitter/user/elonmusk" \
  -H "X-API-Key: tda_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"cookie": "ct0=abc123;auth_token=xyz789", "proxy": "http://user:pass@proxy:8080"}'

​
Example Response

{
  "data": {
    "id": "44196397",
    "userName": "elonmusk",
    "name": "Elon Musk",
    "screen_name": "elonmusk",
    "followers": 236242504,
    "following": 1292,
    "is_blue_verified": true,
    "description": "...",
    "profile_image_url": "https://pbs.twimg.com/..."
  }
}
This request costs 16 credits (User Profile lookup). Check the Billing page for full pricing details.

​
What’s Next?

SDKs

Python & JavaScript client libraries

Authentication

Learn about API key authentication

Proxy & Cookies

Understand how to pass proxy and cookies

API Reference

Explore all 56 endpoints

Billing

Understand pricing and credits

​
Quickstart FAQ

Under 5 minutes. Register, get your API key, add credits ($10 minimum), and make your first call. No approval process or waiting period.
No. Read-only GET endpoints (user lookups, followers, tweets, search) use a server-side pool — you only need your API key. POST endpoints for write actions (tweet, like, follow, DM) require your own Twitter cookies and proxy.
All requests go to https://api.apitwitter.com. The API key is passed via the X-API-Key HTTP header.