# What Endpoints Does the Twitter API Have? | TwitterAPIs
Canonical: https://www.twitterapis.com/answers/what-are-the-twitter-api-endpoints
Description: A map of all 94 endpoints: 60 reads, 34 writes, fifteen families from Search to Monitoring, with the seven price tiers and the nineteen that cost nothing.
Generated: 2026-08-26T06:52:18.866Z
---[Pricing](/pricing)[Docs](https://docs.twitterapis.com)[Blog](/blogs)

Compare and Tools

[MCP Server](/mcp)[Integrations](/integrations)[Language Clients](/sdk)[Free Tools](/tools)[Twitter ID Finder](/tools/twitter-id-finder)[Twitter API Cost Calculator](/twitter-api-cost-calculator)[Twitter Search API](/twitter-search-api)[Twitter Followers API](/twitter-followers-api)[Twitter Scraper](/twitter-scraper)[Twitter API Use Cases](/twitter-api-usecases)[Twitter API Rate Limits](/twitter-api-rate-limits)[Twitter Unofficial API](/twitter-unofficial-api)[Twitter Free API](/twitter-free-api)[Twitter API Alternatives](/twitter-api-alternatives)[TwitterAPIs vs Tweepy](/twitterapis-vs-tweepy)[TwitterAPIs vs RapidAPI](/twitterapis-vs-rapidapi)[TwitterAPIs vs GetXAPI](/twitterapis-vs-getxapi)

Company

[About](/about)[Status](/status)[Affiliates](/affiliates)[Trust](/privacy-and-data-handling)[Changelog](/changelog)[Contact](/contact)

[Start Free](/signup)

1.  [Home](/)
2.  /[Answers](/answers)
3.  /What endpoints does the Twitter API have?

# What endpoints does the Twitter API have?

Last updated August 24, 2026

The surface is 94 endpoints, 60 of them reads and 34 writes, grouped into fifteen families in the catalog. Monitoring is the largest at 14 paths, then Write Actions and Session Reads at 12 each, User Reads at 11, Articles at 9. Nineteen of the 94 bill nothing, and most of the rest sit at the standard rate per call.

Every rate here is the pricing TwitterAPIs publishes. The billed rate is $0.0008 per call; $0.04 per 1,000 tweets is derived from it at a full 20-tweet page, which is the default page size rather than a guaranteed yield (source: [twitterapis.com/pricing](/pricing)).

## How the catalog is grouped

Fifteen named families cover all 94 paths, and the counts sum rather than approximate. Search holds 2, Tweet Details 5, User Reads 11, Follower Graph 5, List Data 7, Session Reads 12, Write Actions 12, Direct Messages 3, Articles 9, Trends 2, Spaces 1, Communities 7, Grok 2, Account 2 and Monitoring 14. Bookmarks are not a family of their own; they sit inside Session Reads with the home timeline and the block and mute lists, because all of those read the session you registered rather than a public profile. There is no media family either: the upload write and the processing-status read both live in Write Actions. The ordering above is the order the catalog itself renders them in.

## Which families are read-only

Eight of the fifteen contain no writes at all: Search, Tweet Details, User Reads, Follower Graph, Communities, Spaces, Trends and Account. The mixed families split in ways worth knowing before you plan a job. Write Actions is 11 writes against a single read, media/status, which polls the processing state of an upload rather than uploading anything and therefore bills and counts as a read. Monitoring runs 6 reads to 8 writes, Articles 2 to 7, List Data 4 to 3, Session Reads 9 to 3, Direct Messages 2 to 1, and Grok is one of each. Across the whole surface reads outnumber writes, 60 to 34. Spaces is the smallest family at a single path, one read of a Space by its id.

## What each price tier holds

Seven tiers partition the 94, and the partition is asserted tier by tier rather than by its total, because moving one endpoint between two buckets leaves a sum unchanged and hides the error. Sixty sit at the standard $0.0008, which also covers every simple write. Eleven are premium at $0.0016. One is $0.0024, two are $0.004, one is $0.01, and nineteen are free. The premium eleven are tweet/create, dm/send, the two DM reads dm/list and dm/conversation, six article writes, and list/create, which costs twice what its two membership-write siblings do and is the one people guess wrongly from the family name. One tier is deliberately empty: simple writes bill at the read rate, so they already sit inside the standard sixty rather than in a bucket of their own.

## The nineteen that bill nothing

Every management route is zero-rated. That means account/me and account/payments, customer/session and its delete counterpart, grok/config, and all fourteen Monitoring paths, which cover webhook create, list, delete and test, monitor create, list, delete and update, the per-monitor and account-wide health reads, the deliveries feed, and three compatibility paths translating an older request shape onto the same system. Five plus fourteen is the nineteen. Revoking a stored session is priced at zero as a property rather than as a discount: a route that charged would return a payment error to somebody at a zero balance trying to delete their own credentials. The three compatibility paths carry no price entry of their own and resolve onto the monitor slugs through an alias table, which is how they stay free without a duplicated row.

## The reads and writes that cost more

Five things sit above the standard rate. user/tweets/complete is $0.0024 because it pages internally and returns a large slice of an account's history in one response instead of a cursor page. tweet/thread and grok/chat are both $0.004, priced for the wall-clock cost of a long connection hold and the upstream work behind it rather than for any model tokens, since the customer's own account does the inference. dm/list, dm/conversation and dm/send are $0.0016 each. user/user\_login is $0.01 and is billed only when the login actually succeeds, so a challenged or refused attempt costs nothing. Everything else is the standard rate or free, so six numbers describe the entire catalog: zero, $0.0008, $0.0016, $0.0024, $0.004 and $0.01.

## Writes that bill at the read rate

Most write actions cost exactly what a read costs. A like, a retweet, a bookmark, a follow, each of their undos, a post delete, a media upload and the two List membership writes all bill $0.0008, which is why the constant for a simple write and the constant for a read carry the same value in the pricing source. Only creation is priced up: a new post, a DM send, six of the nine article operations, and list/create. If you are estimating a write-heavy job, count the creations separately and file everything else in alongside your reads. media/upload is the one that surprises people, since a large payload still bills the same eight hundredths of a cent that a like does.

## Which routes need a registered X session

Authentication is one key everywhere, but a subset of routes additionally needs an X session registered against that key, because they act as an account rather than reading from a shared pool. That covers every Session Read, every Write Action, all three Direct Message routes, the Article operations except reading a published article by its announcement post, both Grok routes, and the three List writes, since a List belongs to an account. Community reads are pooled instead, which is why the four fields describing the caller's own relationship to a community always come back null. Registering that session and revoking it are both free calls, so the credential step never costs anything on its own.

## Two paths in one family can answer different questions

Names are a poor guide and parameter sets are a good one. list/tweets runs against the search index, so it accepts since, until and include\_replies and returns no retweets, while list/timeline uses X's native ordering, carries members' retweets and takes no filters at all. They are two capabilities rather than two spellings of one. user/status works the same way: it separates alive, suspended, not\_found and unavailable and answers 200 for every case, where a plain profile lookup collapses a ban, a deletion and a typo into one 404 you cannot branch on. The quote reader is a third case: X exposes no dedicated quote-tweet operation, so it runs a search against the index and its count is what that search returned rather than the post's own quote figure.

## One ceiling covers all 94

There is no per-endpoint quota and no tier to upgrade into. A key is allowed 600 requests a minute and 20 concurrent, applied identically to every route, and crossing either returns 429 with a Retry-After header. That flatness is what makes a job estimable: pick a worker count at or under twenty and throughput follows arithmetic instead of a lookup table. The same 94 paths are published as agent tools, 60 read and 34 write, so an agent client sees the surface a REST caller sees, though that package ships on its own release cadence and the equality is not a rule. Two narrower caps sit alongside the ceiling and are documented rather than hidden, one on direct-message sending and one on credential logins. Per our published rates: $0.0016 a call.

## The fifteen families, by size and read to write split

Family

Endpoints

Reads

Writes

Rate

Monitoring

14

6

8

free

Session Reads

12

9

3

standard

Write Actions

12

1

11

mixed

User Reads

11

11

0

mixed

Articles

9

2

7

mixed

List Data

7

4

3

mixed

Communities

7

7

0

standard

Tweet Details

5

5

0

mixed

Follower Graph

5

5

0

standard

Direct Messages

3

2

1

premium

Search

2

2

0

standard

Trends

2

2

0

standard

Grok

2

1

1

mixed

Account

2

2

0

free

Spaces

1

1

0

standard

> Rate limits are the number of requests that can be made to an endpoint within a given time window.

X Developer Platform, rate limits documentation. [Source](https://docs.x.com/x-api/fundamentals/rate-limits)

## Questions and answers

How many Twitter API endpoints are there in total?

Ninety-four unique public paths, 60 reads and 34 writes. The figure is derived from the router that serves them rather than counted off a documentation page, with four infrastructure routes and one alias excluded from the total. The same 94 are published as agent tools carrying the same read and write split, so a tool-calling client and a REST client are looking at one surface.

Which family has the most endpoints?

Monitoring, at 14 paths, which is larger than either Session Reads or Write Actions at 12 apiece. It holds four webhook routes, four monitor management routes, two health reads, the deliveries feed and three compatibility paths shaped like an older streaming interface. Every one of the fourteen is free to call, so the biggest family also happens to be the cheapest one to build against.

Are the write endpoints priced differently from reads?

Mostly not. A like, retweet, bookmark, follow, their undos, a delete and a media upload all bill at the read rate. The exceptions are creations: a post at $0.0016, a DM send at the same, six of the nine article operations, and list/create, which costs twice what adding or removing a List member costs. Login is the outlier at $0.01 and charges only on success.

Is there a rate limit across all these endpoints?

One ceiling covers the whole surface instead of a window per route. A key gets 600 requests a minute and 20 in flight, and anything past either answers 429 with a Retry-After header. Because the limit does not vary by endpoint, a cheap search loop and an expensive expansion loop draw on the same allowance, which turns concurrency planning into arithmetic rather than a per-route table.

Where do bookmarks and DMs sit in the catalog?

Bookmarks live inside Session Reads, next to the home timeline, the block and mute lists and the two bookmark-folder reads, because every one of those reads your own registered session rather than a public profile. Direct Messages is a family of three, two reads and a send, all priced at $0.0016. Neither a bookmark list nor a DM thread is public, which is why both need a session.

Do all 94 endpoints work with a single key?

For authentication, yes. One credential reaches every family and there is no per-endpoint entitlement to purchase. The routes that act on an account need something extra, which is a registered X session, because they run as your account instead of a pooled one. That covers Session Reads, Write Actions, Direct Messages, most Article operations, both Grok routes and the List writes.

Which endpoints cost more than the standard rate?

Fifteen of the 94, once you set the free ones aside. Eleven are $0.0016, covering post creation, DM send, the two DM reads, six article writes and list/create. One is $0.0024, the full-history read. Two are $0.004, thread expansion and Grok chat. One is $0.01, the credential login, and it charges only when the login succeeds. The remaining sixty are all the standard read rate, simple writes included.

Are there endpoints you charge for but do not document?

Three billing keys have no route serving them: user/update\_profile, user/update\_avatar and user/update\_banner. They are priced but unpublished, so they carry no public price row and nothing can call them. One route went the other way and was unpublished deliberately, the batch user lookup, because X refuses batch resolution for pooled sessions. The per-id lookup user/info\_by\_id replaced it. Those three write routes are commented out upstream because the profile-update endpoints they wrapped answer 404 on every host.

What is the difference between list/tweets and list/timeline?

Their parameter sets, which is the honest way to tell two capabilities apart. list/tweets is backed by the search index, so it takes since, until and include\_replies and returns no retweets. list/timeline is X's own List feed, so it carries members' retweets and X's ordering and accepts no filters at all. Both bill $0.0008, so the choice is about what you need rather than cost.

Do the agent tools cover the same 94 endpoints?

Today yes, at 94 tools split 60 read and 34 write, matching the REST surface one for one. That equality is a property of the current catalog rather than a rule: the package is built and released on its own cadence, and the two have already drifted apart once, so the published tool list is what to check instead of an endpoint count read off a page.

## Keep reading

-   [Twitter REST API](/twitter-rest-api?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-what-are-the-twitter-api-endpoints)
-   [Endpoint catalog](https://docs.twitterapis.com/docs)
-   [Per-call pricing](/pricing?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-what-are-the-twitter-api-endpoints)
-   [Twitter API rate limits](/twitter-api-rate-limits?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-what-are-the-twitter-api-endpoints)
-   [MCP server](/mcp?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-what-are-the-twitter-api-endpoints)
-   [How do you get tweets programmatically?](/answers/how-to-get-tweets-programmatically?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-what-are-the-twitter-api-endpoints)
-   [The Grok endpoint](/answers/how-to-use-grok-through-an-api?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-what-are-the-twitter-api-endpoints)
-   [The Spaces endpoint](/answers/how-to-get-twitter-spaces-data-api?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-what-are-the-twitter-api-endpoints)
-   [The trends endpoints](/answers/how-to-get-twitter-trends-api?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-what-are-the-twitter-api-endpoints)

### Start with $0.50 in free credits

No credit card. Roughly 12,500 tweets to test every endpoint.

[Get your API key](/signup?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-what-are-the-twitter-api-endpoints)[See pricing](/twitter-rest-api?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-what-are-the-twitter-api-endpoints)

[

TwitterAPIs](/)

The cheapest pay-as-you-go Twitter and X API. $0.0008 per call, which works out to $0.04 per 1,000 tweets on a full 20-tweet page. No subscriptions and no developer account.

## Product / API

-   [Pricing](/pricing)
-   [Pay-Per-Use Pricing](/pay-per-use-pricing)
-   [Cost Calculator](/twitter-api-cost-calculator)
-   [Rate Limits](/twitter-api-rate-limits)
-   [MCP Server](/mcp)
-   [Integrations](/integrations)
-   [Language Clients](/sdk)
-   [Changelog](/changelog)
-   [Status](/status)

## Developers

-   [Documentation](https://docs.twitterapis.com)
-   [API Reference](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search)
-   [User Info](https://docs.twitterapis.com/docs/reference/user-reads/user-info)
-   [User Tweets](https://docs.twitterapis.com/docs/reference/user-reads/user-tweets)
-   [Advanced Search](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search)
-   [Verified Followers](https://docs.twitterapis.com/docs/reference/follower-graph/user-verified-followers)

## Resources / Compare

-   [Answers](/answers)
-   [Reviews](/reviews)
-   [Free Tools](/tools)
-   [Twitter ID Finder](/tools/twitter-id-finder)
-   [Get a Twitter API Key](/twitter-api-key)
-   [Official X API Comparison](/twitter-api-pricing)
-   [Twitter API Use Cases](/twitter-api-usecases)
-   [Twitter API Alternatives](/twitter-api-alternatives)
-   [Twitter Unofficial API](/twitter-unofficial-api)
-   [Twitter Free API](/twitter-free-api)
-   [TwitterAPIs vs twitterapi.io](/twitterapis-vs-twitterapi-io)
-   [TwitterAPIs vs GetXAPI](/twitterapis-vs-getxapi)
-   [TwitterAPIs vs TweetAPI](/twitterapis-vs-tweetapi)
-   [TwitterAPIs vs TwexAPI](/twitterapis-vs-twexapi)
-   [TwitterAPIs vs RapidAPI](/twitterapis-vs-rapidapi)

## Legal

-   [About](/about)
-   [Security](/security)
-   [Trust](/privacy-and-data-handling)
-   [Terms of Service](/terms-of-service)
-   [Affiliates](/affiliates)
-   [Contact](/contact)
-   [Jobs](/jobs)

© 2026 TwitterAPIs. All rights reserved.

TwitterAPIs is an independent third-party API for developers and researchers. Not affiliated with, endorsed by, or sponsored by X Corp.

All systems operational