Twitter API endpoints: the ones developers actually use
Twitter API endpoints by job: search, users, timelines, followers, replies and lists, what each REST call returns, plus quick answers to common Twitter API questions.
Piyushh · November 13, 2026 · 5 min read

The Twitter API endpoints developers use most fall into nine jobs: search tweets, look up one tweet, look up a user, read a timeline, list followers and following, read replies, find retweeters, find mentions and read list members. This page maps each job to a REST call you can make today, with its cost and a link to the docs. After that it answers the general Twitter API questions people search for.
According to the overview on docs.x.com (checked 2026-11-13), X's API v2 lives at api.x.com/2, uses Bearer authentication and bills pay-per-usage against purchased credits. That page lists six resource groups (Posts, Users, Spaces, Direct Messages, Lists and Trends) and describes v1.1 as the previous version, with limited support. The examples here use ChatterAPI's endpoints, which are plain REST and don't need an X developer app. We are independent of X.
Twitter API endpoints by job
Base URL: https://api.chatterapi.com/v1. Auth: Authorization: Bearer <key>. Every response has the same envelope, data, page, credits, requestId, cached.
| Job | Endpoint | Credits |
|---|---|---|
| Search tweets | GET /x/tweets/search | 2 per page |
| One tweet by id | GET /x/tweets/{id} | 2 |
| User profile | GET /x/users/{handle} | 2 |
| User timeline | GET /x/users/{handle}/tweets | 2 per page |
| Mentions of a handle | GET /x/users/{handle}/mentions | 2 per page |
| Followers | GET /x/users/{handle}/followers | 2 per page |
| Following | GET /x/users/{handle}/following | 2 per page |
| Replies to a tweet | GET /x/tweets/{id}/replies | 2 per page |
| Retweeters | GET /x/tweets/{id}/retweeters | 2 per page |
| List members | GET /x/lists/{id}/members | 2 per page |
A page holds about 20 rows, and failed calls cost nothing. The full list is in the endpoint index and the X docs.
Search
The search endpoint takes keywords and X search operators in q. It also takes sort (latest or top), since and until as YYYY-MM-DD, lang as two letters, and includeRetweets.
curl "https://api.chatterapi.com/v1/x/tweets/search?q=%22crm%20recommendation%22&sort=latest&lang=en" \
-H "Authorization: Bearer $CHATTERAPI_KEY"
Each tweet comes back with id, text, url, createdAt, likes, retweets, replies, views and an author object. You can try queries in the free tweet search tool. For date ranges, see how to search tweets by date.
One tweet, and tweet ids
Pass a tweet id and you get that one post with its counts and author. This also answers the "twitter id api" question: the id is the long number at the end of a tweet URL. The free tweet lookup does the same thing in a browser.
Users
The profile call answers "twitter api get user", "get user info" and "get user id". It returns the numeric id, handle, name, bio, followers, following, verified flags, canDm, location, link and createdAt. Try it in the free X user lookup. Two more profile tools have their own endpoints: x.user_location for the profile location text, and x.account_analytics for posting rate and engagement across the latest 20 posts, at 4 credits.
Timelines, mentions and replies
/x/users/{handle}/tweets returns recent posts, newest first. Pass includeRetweets=false to get only the account's own posts. Mentions return recent posts that @mention a handle, and replies return the answers under one tweet. The free timeline scraper and replies exporter run on these.
Followers and following
Followers and following return about 20 profiles per page, with a cursor. If you're looking for the "twitter friends api", this is it: X calls the accounts you follow friends, and the call is following. Verified followers, follower search by bio and a fake-follower estimate each have their own endpoint. See the follower exporter and our export guide.
Lists
List members takes a list id or an x.com/i/lists/<id> URL and returns the list's member profiles.
Actions are separate
ChatterAPI also has four X actions that need an X account you connect yourself in the dashboard: send a DM (10 credits), follow (5), like (5) and tweet (5). Reads work without an X account. These actions run under safe limits, so they aren't meant for bulk use.
What we do not have
Before you spend a call looking for them: ChatterAPI has no streaming or push, no trends endpoint, no endpoint that lists a user's likes, no DM webhooks and no email addresses. Everything works by polling.
Pagination in one paragraph
List endpoints return page.nextCursor and page.hasMore. Pass the cursor back as cursor until hasMore is false. Cursors are opaque, so don't parse them. The Twitter API Python guide has a working loop.
Quick answers to common Twitter API questions
Both APIs are REST. X's v2 API is REST over HTTPS at api.x.com/2, and so is ours. That covers "twitter rest api", "rest api twitter", "twitter api rest" and the rest of that family.
Both are served over HTTPS. We did not check X's specific TLS configuration and do not claim details beyond that.
People use the Twitter API to read and analyse posts and profiles, monitor brands, build datasets, power agents, and post from their own account. See what the X API documentation covers.
To apply for access to X's own API, start in its developer console. See how to get an X API key. For a hosted API you sign up and copy a key. Our Twitter API v2 guide covers the versions.
X's overview describes v1.1, which some still call "twitter standard api", as limited support and tells new projects to use v2 (checked 2026-11-13). Old tutorials built on v1.1 are out of date. We did not verify which v1.1 endpoints still respond.
The big change to the Twitter API was pricing. X moved to pay-per-usage billing, covered in is the X API free and X API pricing. Prices change, so we cite none here.
We cannot tell you whether X's own API is down. For ours, check the status page.
To test endpoints, use curl, the free tools, or the API playground in the dashboard, which works as an explorer and tester. A test key returns one recorded real response per endpoint for free, and that is the safest way to see the shape.
The "time", "place" and "url" parameters work like this. Time is since and until on search and createdAt on every row, in UTC. Place is not a parameter of ours: see Twitter API location. For URLs, tweet rows carry a url, and the lookups accept ids.
Any language works, because it is HTTP and JSON. Go, JavaScript, Python and curl all work. Examples for Python and agents: Python and the X MCP server.
As for "twitter api me", X's API has an endpoint for the authenticated user, but we did not verify its exact name today. With ChatterAPI you look up any handle, including yours.
Try an endpoint in the playground
Open the X docs to run any endpoint above with a key, or sign up to start with a free test key.