review galore

Review · Social data APIs

X API review

A flexible API for X data and actions, but usage charges and technical setup make it a poor fit for casual automation.

6.1/10Review Galore score

We may earn a commission if you buy through links on this page. It never changes a score or a ranking. How we make money

The bottom line

Useful for building on X, but budget carefully: there’s no free plan and charges follow usage.

A small team only needs X API if it is building a product or workflow that must read or act on X data. It covers posts, search, users, streams, messages and more, but it is an API for developers rather than a ready-made social media tool.

Pay-Per-Usage has no base subscription, but reads and actions carry charges and prepaid credits can run out. There is no current free plan listed, so teams with light needs should compare the likely API bill with the value of automating their work.

Good fit if

  • Teams building X-connected products
  • Developers needing X data access
  • Apps with measurable API usage

Skip it if

  • Teams wanting free API access
  • Nontechnical social media scheduling
  • Budgets needing fixed monthly costs
X API homepage
X API homepage, captured Nov 10, 2026

ScoresHow it rates

  • Features8
  • Ease of use4
  • Value for money5
  • Support4
  • User sentiment3

What works

  • Covers posts, search, streams and users
  • Pay-Per-Usage has no base subscription
  • Supports reading and writing X data
  • Enterprise contracts offer custom limits
  • OAuth provides account authorization

What doesn't

  • No current free plan is listed
  • Usage charges can be hard to forecast
  • Prepaid credits can stop requests
  • Enterprise pricing is custom
  • Not a ready-made scheduling tool

01Who X API is for

A team of one to ten should consider X API when its own product or internal workflow needs to read, analyze or publish X data. It provides access to posts, search, streams, user information, direct messages, lists and other account functions. Developers can also create, delete, like, repost or bookmark posts, subject to the available API access and usage charges.

This is a developer tool, not a social media dashboard for a small marketing team. You will need an application that uses the API and OAuth, plus someone who can build or maintain that connection. A solo developer or small product team may find the flexibility worthwhile if X data is central to what they are making. If the job is simply scheduling a few posts, compare the API bill and build effort against a social publishing tool before committing. The pay-per-usage model avoids a base subscription, but it does not make high-volume use free.

02X API free plan and trial

X API does not list a current free plan or free trial. Legacy Free is retired; its former limits were 100 post reads and 500 posts per month at app level, with one app ID. Those limits are historical, not a free way to start now.

The cheapest current option is Pay-Per-Usage, which has no base subscription and uses prepaid credits. The pricing page lists 3,000,000 post reads per monthly billing cycle, a $0.005 charge per post read, and rate limits of 100 posts per 15 minutes per user and 10,000 posts per 24 hours per app. Other reads and actions have separate charges. Requests stop when credits reach zero or a user-defined spending limit is reached. Before building, estimate each type of request and load credits accordingly; a zero-dollar monthly base does not mean zero-cost use.

03What a small team pays for X API

Pay-Per-Usage has a $0 base price, not a per-seat subscription. One person, a team of three or a team of five pays the same API rates for the same request volume; adding seats does not create a published seat charge. The actual monthly bill depends on how many reads and actions the application makes, so the pricing page does not give a set team total.

The listed post-read rate is $0.005. Add-ons include $0.010 per user read, follower or following read, DM event read, or summoned reply; $0.001 per owned-data read; $0.015 per post created or direct message sent; and $0.200 per post created with a URL. Set a spending limit, because requests stop when credits or that limit run out, and overage costs are not published.

Legacy Basic is retired, but its former price was $200 monthly or $175 per month when billed annually ($2,100 for a year). That is not a current plan to budget for. Enterprise pricing is custom.

Full X API pricing breakdown →

04Getting started with X API

Plan for developer setup, not a quick switch in a social media app. X API uses OAuth, so the application needs an authorization flow and code that sends requests for the X functions it needs. A useful first step is to list the actions and data the workflow requires, then estimate their separate usage charges before choosing a spending limit.

The feature set spans post management, search, streams, users, messages and metrics; connecting those pieces to a product or internal workflow will take engineering work. The published material does not identify a ready-made integration directory or a specific setup time, so ask X or your developer what is required for your use case. Reddit users discuss building their own posting automation, including a thread where the author describes a custom backend. That is a sign of the technical work involved, not an official setup recommendation. No named third-party integrations are listed here.

05When small teams outgrow X API

X API is not priced by seats, so a growing team does not automatically hit a per-user plan jump. The pressure comes from request volume, rate limits and the cost of the actions the product performs. Pay-Per-Usage lists a 3,000,000 post-read monthly billing-cycle figure, and Enterprise offers custom limits above that cap. Its contract price is custom, so ask X for a quote before relying on higher limits.

A workflow can also run into action-specific costs: a URL post is listed at $0.200, compared with $0.015 for a post created without that charge. Requests stop when credits or a user-defined spending limit are exhausted. One Reddit thread describes an agency paying $200 a month on a legacy Basic tier just to schedule and post; that tier is now retired, so it is not a current price point. Other Reddit users complain about API costs or discuss unofficial approaches. Those discussions underline the budget concern, but unofficial access methods are not a substitute for confirmed API terms.

From the threadsWhat users say

Reddit sentiment is mostly skeptical about X API costs, with users discussing workarounds and criticizing the economics of automation. Some commenters appreciate shared tools, but the tone is not broadly enthusiastic about paying for API access.

Cost frustration
$200/month for what is essentially a scheduled POST request
r/n8n · view thread
Unofficial workarounds
This is very cool thank you for sharing
r/n8n · view thread
Business skepticism
X wants to make money
r/webdev · view thread
Posting limitations
Currently only single tweets
r/n8n · view thread

Questions people ask

Is X API free or paid?

X API does not list a current free plan or free trial. The current Pay-Per-Usage option has no base subscription, but charges apply to reads and actions. Legacy Free is retired, so its old monthly limits do not provide free access today.

What does X API Pay-Per-Usage cost?

There is no base subscription charge. The pricing page lists $0.005 per post read, with other actions charged separately, such as $0.015 per post created or direct message sent. Your total depends on request volume and the types of requests your app makes.

Does X API charge by user or seat?

The current Pay-Per-Usage option is not listed as a per-seat plan. A one-person app and a five-person team pay according to API usage, not a published seat price. Some API actions, including user reads, have their own usage charges.

What happens when API credits run out?

Requests stop when credits reach zero or a user-defined spending limit is reached. The pricing page does not publish overage costs, so set a limit and ask X how your application can resume requests after credits are replenished.

Can a small team get higher API limits?

Pay-Per-Usage lists a 3,000,000 post-read monthly billing-cycle figure. Enterprise offers custom contracts and limits above that cap, but the price is not listed. Ask X for a quote and confirm the limits your application needs.

Sources

  1. X API homepage
  2. X API pricing, compiled via web search from blotato.com, twitterapi.io, climbx.so, outstand.so, upload-post.com, sorsa.io
  3. Reddit: Open-sourced the setup we use to post tweets without paying for X's API
  4. Reddit: Elon just made X API way cheaper for reads, and straight up said people should build apps on top of it. Huge W
  5. Reddit: The X API is expensive af. Any alternatives?
  6. Reddit: Open-sourced the setup we use to post tweets without paying for X's API [no promotion]