X API Pricing Explained: What Marketers Pay Per Post and Read

For most marketing teams, X API pricing used to be somebody else’s problem. The scheduling tool paid X, the listening tool paid X, and the cost was buried inside a seat license. That changed in 2026. X replaced fixed monthly tiers with metered billing for new developers in February, then repriced several actions in April, including a sharp increase for posts that carry a link. Because nearly every B2B post exists to send someone to a landing page, that one line item now affects tool contracts, publishing habits and the economics of social listening. This guide explains the rates, shows the arithmetic and gives you questions to put to vendors. It is part of the Kurums Social Media Marketing Hub.

What is X API pricing in 2026 and why does it matter to marketers?

X API pricing is the fee schedule X charges software companies and in-house developers each time their code publishes, reads or interacts with content on the platform. Marketers rarely pay it directly, yet it determines what scheduling, listening and customer care tools can afford to offer.

The application programming interface, or API, is the pipe that connects X to everything outside the X app. When a social media manager schedules a post in a third-party dashboard, the dashboard calls the X API at the scheduled minute. When a listening tool reports that mentions of a competitor rose last week, it has pulled those posts through the API. When a customer care platform routes a complaint to an agent, it received that mention through the API as well.

Until early 2026 new developers bought access in fixed monthly bundles. X’s developer changelog records that the pay-per-use model officially launched on February 6, 2026, together with a new Developer Console, software development kits for Python and TypeScript and a credit system. From that point, new accounts buy credits upfront and each request deducts from the balance in real time. X describes the model on its pricing page as having no subscriptions.

For a marketing leader the practical consequence is that X is now a variable cost inside your tool stack. Your vendors have to decide whether to absorb it, ration it or bill it through. Each choice shows up in your contract in a different way, and the differences are large enough to change which tool is the right one. If you are reviewing options, the Kurums comparison of social media scheduling software is a useful companion to this guide.

How does the pay-per-use model work?

A developer buys credits in the X Developer Console, and every API request deducts an amount that depends on the action. Reads are priced per resource returned, writes are priced per request, and usage is tracked at the level of the individual app.

Three mechanics in X’s documentation matter for budgeting. First, reads are deduplicated within a 24-hour UTC window. If a tool fetches the same post five times in one day, it is charged once; if it fetches the post again tomorrow, it is charged again. Second, developers can set a monthly spending limit, after which X blocks further requests until the next cycle. That protects against runaway bills, and it also means a tool can simply stop working mid-month if its limit is set too low. Third, auto-recharge can top up the balance when it falls below a threshold.

X also separates owned reads from ordinary reads. When an app reads data that belongs to the authenticated account, such as the brand’s own posts, bookmarks or followers, the listed rate is $0.001 per resource. X introduced that category in a pricing update announced on April 16, 2026 and effective April 20. Pulling your own analytics is therefore cheap. Reading other people’s conversations is where costs accumulate.

What does it cost to publish posts through the API?

X lists $0.015 for each post created through the API and $0.20 for each post that contains a URL, as of October 2026. A link post therefore costs a little over thirteen times as much to publish as a post without one.

The split dates from the April 2026 update. X’s changelog states that post creation was adjusted to $0.015 per post and that posts containing URLs increased to $0.20 per post. Trade publication The Meridiem calculated the change for link posts as a roughly 1,900% increase on the earlier rate. X did not frame the change as a marketing policy in its documentation, but the effect on publishers is plain: the API now charges a premium for the kind of post that sends traffic off the platform.

Source: X developer documentation pricing page, checked October 2026. Rates are in US dollars and can change, so confirm them on X’s official pricing page before building a budget.

For a single brand these numbers look small. A team that schedules ten posts a day, all with links, creates about 300 link posts a month, or $60 in API cost. The pressure appears at vendor scale. A scheduling platform whose customers collectively publish one million link posts a month would owe X $200,000 for that month at list rates. That is a hypothetical illustration of the arithmetic, and it explains why vendors have had to revisit how they package X.

What does it cost to read posts for listening and analytics?

Reading a post costs $0.005 and reading a user profile costs $0.010 at X’s listed rates. A listening query that returns 100,000 posts costs $500, and pay-per-use accounts cannot read more than 3 million posts in one billing cycle.

Read pricing is charged per resource returned. Search results, timelines, mentions, filtered streams and list lookups all count toward the post read total, according to X’s usage and billing documentation. Follower and following lookups are priced at $0.010 per resource, likes at $0.001, and lists, Spaces and Communities at $0.005.

The 3 million cap sets a ceiling of $15,000 a month in post reads on a single pay-per-use account. A mid-market brand tracking its own name, three competitors and a handful of category terms can stay well inside that. A consumer brand in a noisy category, or an agency running listening for forty clients, may not. That is the line where a listening vendor needs an Enterprise agreement with X, and where your own quota inside the vendor’s product starts to matter.

Webhook deliveries are billed too. X’s Activity API charges per event delivered, with examples in the documentation of $0.005 for a post creation event and $0.010 for a follow event. Customer care tools that rely on real-time mention delivery carry this cost for every inbound message.

What happened to the legacy Basic and Pro tiers?

X’s changelog entry for the February 6, 2026 launch states that Basic and Pro plans remained available at that time, and that legacy Free tier users received a one-time $10 voucher. Current pricing documentation describes only pay-per-use and Enterprise.

Third-party developer guides published during 2026 consistently report the legacy plans at $200 a month for Basic and $5,000 a month for Pro, and describe them as closed to new signups, with existing subscribers allowed to stay. X’s own pricing and billing pages, as checked in October 2026, make no reference to those plans, so treat the legacy details as vendor-reported unless your developer team confirms them in its own console.

Why should a marketer care about a retired price list? Because it shapes vendor behavior. A tool that still sits on a flat legacy plan has a fixed X bill and little reason to meter your posting. A tool that signed up after February 2026, or that has been moved to metered billing, pays for every action. Two products with identical feature pages can therefore have very different cost structures underneath, and different incentives to limit your usage.

The April update also removed some data from self-serve access. X’s changelog notes that Following, Likes and Quote-Posts were removed from self-serve tiers. If a dashboard widget that showed who quoted your posts has disappeared from a tool this year, that is the probable cause.

How do scheduling and listening vendors pass the cost on?

Vendors recover X API costs in five ways: raising plan prices, selling X as a paid add-on, limiting the number of X posts or profiles per plan, asking customers to connect their own X developer account, or dropping X features such as inbox and listening.

We could not confirm specific 2026 price changes for named vendors from their own published statements, so this section describes the patterns to look for instead of attributing policies to particular companies. Check each vendor’s current pricing page and terms.

• Blended price increase. The vendor raises all plans slightly and keeps X inside. Simple for buyers. Customers who do not use X subsidize those who do.
• X add-on. X publishing or listening becomes a separately priced module. Transparent, and easy to cancel if X is a minor channel for you.
• Quotas. Plans include a fixed number of X posts, link posts or mention reads per month. Watch for what happens at the limit: hard stop, overage fee or forced upgrade.
• Bring your own key. You create an X developer account, buy credits and paste your credentials into the tool. You see the true cost and carry the administrative work, including spending limits and card management.
• Feature removal. The tool keeps basic publishing and drops reads: no unified inbox for X, no competitor tracking, thinner analytics.

Pass-through models are the most honest about cost and the least predictable for budgeting. Quota models are predictable until a campaign month breaks the limit. Neither is wrong. What matters is that you know which one you have signed. The Kurums review of social media management software covers how the major suites package channels.

How much should a marketing team budget for X API costs?

Most teams should budget in three lines: publishing, owned analytics and listening. Publishing and owned analytics rarely exceed tens of dollars a month for a single brand. Listening is the line that scales into hundreds or thousands.

The table below applies X’s listed rates to three illustrative usage profiles. They are arithmetic examples built from the public price list, and your vendor’s packaging will add margin or cap usage.

Two conclusions follow. Publishing cost is trivial for one brand and material only in aggregate, which is why it reaches you through vendor packaging. Listening cost is real at the level of a single brand and should be scoped as deliberately as a media buy. Decide which queries you need daily, which weekly and which only during a launch or a crisis. For the measurement side, see the Kurums guide to which social media metrics matter. If predictable reach is the goal, compare the listening line with paid placements; the X Ads guide for business covers objectives, bidding and tracking.

How can teams reduce X API costs without posting less?

The largest savings come from changing how links are published, narrowing listening queries and relying on owned reads for reporting. None of these requires cutting output.

Start with links. A post without a URL costs $0.015 to publish through the API, and a post with one costs $0.20. Some teams now publish the main post without a link and add the link in a reply, or post natively from the X app for link-heavy announcements. Be careful with the reply approach: a reply that contains a URL is still a post containing a URL, so the saving only exists if the link reply is posted natively or if the first post alone carries the message. The stronger argument for fewer links is distribution. As the B2B strategy guide for X explains, independent data suggests link posts earn less engagement than text or video.

1. Audit link frequency. Reserve links for posts where the click is the goal, and let commentary, data points and threads stand on their own.
2. Tighten listening queries. Exclude reposts, add language filters and remove ambiguous keywords. Every irrelevant post returned is a paid read.
3. Lengthen refresh intervals. Deduplication applies within a UTC day. Pulling the same competitor timeline hourly costs the same as daily for old posts, but dashboards that re-pull across days pay again.
4. Use owned reads for reporting. Your own account’s analytics are priced at a fifth of ordinary post reads.
5. Set spending limits and alerts. If you run your own developer account, cap monthly spend and review usage by endpoint in the console.

When does an Enterprise API contract make sense?

An Enterprise agreement is necessary when a single organization needs more than 3 million post reads a month, full-volume streams or negotiated rate limits. X prices these contracts on request and publishes no rate card for them.

X’s Enterprise documentation lists custom volumes, exclusive endpoints such as volume streams and likes streams, dedicated account management and priority technical support. In practice the buyers are listening platforms, data resellers, large customer care operations and research groups. A brand marketing team almost never needs its own Enterprise contract. It needs a vendor that holds one, with enough headroom that your queries are not throttled during the month that matters.

That makes vendor diligence the real task. Ask whether the vendor’s X data arrives under an Enterprise agreement or a pay-per-use account, how much historical data is included and whether your contract guarantees a volume of mentions. If the vendor cannot answer, assume your listening quota is thinner than the sales deck implies.

Frequently Asked Questions