X API Voucher: Every Twitter (X) API Free-Credit Program, Who Gets It, How It Expires, and What Happens at $0

The X API moved to pay-per-usage pricing: you buy credits in the Developer Console at console.x.com and every request deducts from the balance at per-resource rates. A voucher is simply a free grant to that same balance. X's own wording has shifted between "voucher" (the $500 beta and $10 migration grants) and "free credits" (the current incentives), and the console labels them as free credits.

No code field. The current docs say both incentives "are applied automatically (no code, voucher, or form)" and appear in the Developer Console "within a minute of the qualifying action". For the $500 beta grant, an X staff reply on the developer forum said it "applies automatically after your project is created, approved, and billing is enabled, no voucher code needed". We found no docs.x.com page that describes entering a voucher or promo code: a full-text search of docs.x.com returned the word "voucher" only twice, once in the February 2026 changelog entry about the $10 migration voucher and once in the sentence saying no voucher is needed.

So what does "redeem an X API voucher code" mean? In practice: meet the eligibility condition, then look under Billing → Credits in the Developer Console, where docs.x.com says the incentive credits appear under Free credits (and in Billing → Payments as a transaction). If a third party offers you an "X API voucher code", X documents no place to use one.

One account, one balance. X's PPU Agreement says credits apply "solely to the account you were using when you purchased the Credits" and are not transferable between X accounts, and the free-credits page says incentive credits have no cash value and cannot be withdrawn, refunded or transferred.

The four grants. Four show up in X's own channels. Two are over. One is documented and live. One is only in X staff posts.

How big each announcement was. The October 2025 @XDevelopers beta post promising a $500 voucher to selected users drew 2,387 likes and about 3.2 million views when we collected it. The February 2026 post announcing the $10 voucher drew 259 likes; the October 2026 "$70 in free credits" post drew 427 likes.

The $500 beta voucher. X opened the pay-per-use pilot in October 2025 as "a limited pilot program only, not a full product launch" and said selected users "will receive a $500 voucher to build with the X API". After the February 2026 launch, an X staff reply to a developer missing the $500 said: "The beta has ended and pay-per-use has officially launched. We are no longer running any promos or giving out vouchers." If you are reading an older guide that tells you to apply for the $500, that offer is over.

The $10 migration voucher. The X API changelog entry of February 6, 2026 reads: "Recently active Legacy Free tier users receive a one-time $10 voucher." An X engineer posted on February 10, 2026 that X had "finished provisioning all recently active free accounts with $10 of credits expiring end of March". In a June 2026 forum thread a staff member answered a developer who never received it: "Vouchers have already been distributed for eligible accounts. Your account had to be recently active to qualify."

This is the program most people searching for an X API voucher today actually want. X announced it on October 2, 2026 and changed it on October 13, 2026. The rules below are quoted or paraphrased from the free-credits page on docs.x.com as read this session.

$20 for the first card, after the first purchase. "A one-time $20 in free credits after an account with its first eligible card completes its first purchase of API credits." Adding a card on its own "no longer qualifies (updated October 13, 2026)". You can save the card under Billing information → Add payment method and buy later, or buy credits and keep the card on file; that first purchase does not count against the "no previous payments" rule.

Auto-recharge match, up to $50. When your first automatic recharge actually charges the card, X adds free credits equal to that recharge, capped at $50: a $5 recharge earns $5, $20 earns $20, $100 or $500 earns $50. Turning the setting on grants nothing by itself, a failed charge grants nothing, and accounts that already used auto-recharge when the incentive launched are not eligible.

Stacking. The two are independent, so a new account can receive $70 in total. Both are once per account and once per physical card.

Rolling out. The page also carries a note that the incentives "are currently rolling out. Until they are fully enabled for an account, saving a card or enabling auto-recharge behaves exactly as before and no credit is issued." That sentence is worth reading before you file a support ticket.

Free credits are spent first. docs.x.com: "Free credits are consumed before purchased credits." Any usage on the account eats the free balance before the money you paid.

Incentive credits expire after 3 months. "Unused free credits are removed from your balance at that point; purchased credits are unaffected." The $10 migration voucher had its own deadline (end of March, per X staff). For purchased credits, the X Developer PPU Agreement says "Credits do not expire unless otherwise specified, and are not transferable or refundable except as required by law."

At zero, requests stop. The pricing page says you should add credits "before your balance reaches zero to ensure uninterrupted API access", that a balance can go "slightly negative", and that then "API requests will be blocked until you add credits to cover the negative balance". The agreement adds: "You may not maintain a negative credit balance." Developers and X staff on the forum describe the response as HTTP 402 with a credits-depleted error; docs.x.com itself does not list the 402 body.

The auto-recharge trap after a voucher. On May 20, 2026, X posted a forum notice that before the fix, "if you had redeemed a credit voucher (free credits) and those credits reached zero, the auto-recharge feature would not trigger". From May 21, 2026, "Free credits (from vouchers) will be treated the same as paid credits for the purpose of auto-recharge", so a voucher running out now charges your saved card if auto-recharge is on. X's own recommendation was to review the setting and disable auto-recharge if you do not want charges after the free credits are used up.

Auto-recharge safeguards. docs.x.com lists two: at most one automatic top-up per 5-minute window, and auto-recharge pauses at zero or negative balance until you add credits manually. A spending limit per billing cycle blocks requests once reached.

Monitoring the balance. The console shows the balance live. For posts, X documents a usage endpoint that returns daily post consumption counts, shown below; it reports volume, not dollars.

The most common complaint after the October 2026 incentive launch was a $5 grant where $20 was expected, or no grant at all. Forum titles in the two weeks after the October 13 change include "Received $5 free credit instead of the advertised $20 after first card payment", "$20 first-purchase credit granted as $5" and "Missing $20 free credits after adding payment method and first purchase".

What staff said, word for word. In replies on those threads X Developer support wrote that "the free credits page doesn't list a minimum purchase amount for the $20 credit", restated the conditions (first eligible card, no previous payments, credit or debit not prepaid, card not rewarded before), and said: "If all of that matches your account, a $5 voucher isn't what we'd expect, so we're checking on it and will follow up here." In one thread they added they would follow up "including what the $5 Voucher was". At the time of writing, no staff reply we read stated a cause, so we do not give one.

Checklist before you post on the forum. 1. The date rule. If you only added a card and did not buy credits, you have not qualified since October 13, 2026. 2. Prior payments. Any earlier successful payment on the account, including a Legacy Basic charge, disqualifies the $20. 3. Card history. A card that earned the credit on any account earns nothing again; removing and re-adding "never changes the outcome". 4. Prepaid. Prepaid cards never qualify. 5. Rollout. The incentives are still rolling out. 6. Where to look. Billing → Credits → Free credits, about a minute after the qualifying action.

Where to get help. Staff in several threads moved billing cases to the X Developer Platform billing support form at docs.x.com/forms/billing-support. The PPU Agreement says deduction disputes must be raised within 30 days of the disputed deduction through that form. Do not post card or billing details in public threads; staff asked for that explicitly.

402 with a positive balance. A separate cluster: the console shows free credits but endpoints return 402. In two October 2026 threads, staff wrote that "free promotional credits are generally usable for billable v2 endpoints once the App is correctly enrolled" and that the reported case looked like "an enrollment / credit-bucket mismatch rather than expected behavior", and asked for a billing and enrollment check. If your app is a standalone app outside a pay-per-use project, read our X API 403 guide on client-not-enrolled first.

Since late August 2026, a second meaning of "X API voucher" has taken over on X itself: the credits that come with Grok Bot and X Premium+. None of it is on docs.x.com, so everything here is attributed to the person who posted it.

What was posted. On August 29, 2026, X engineer Santiago (@santiagomed, whose profile reads "building the everything api @X") posted that "on top of the included credits to Grok Bot users, this week we started giving $20 of monthly X API credits to all Premium+ users", and replied "For Premium+ it's monthly". The same day Chris Park, who led X's developer platform, posted that Grok Bot was relaunched with X and "free credits included", and replied the next day: "Premium + gets $20 free credits monthly." @XDevelopers reposted Park's announcement.

What is not documented. We found no docs.x.com page describing the Premium+ grant: not its expiry, whether unused credits roll over, or what happens at renewal. X's help center Premium FAQ (help.x.com/en/using-x/x-premium-faq) blocks automated fetching, so we could not read it this session. When a developer opened a forum thread titled "X and Grok Bot Voucher", staff closed it as "not related to the X Developer Platform" and pointed to the Premium FAQ and @Premium.

What subscribers have reported. In public replies to the staff posts, one Premium+ subscriber reported that the $20 voucher was issued, about $0.93 was used, and the balance was zeroed and marked expired around the subscription renewal, with no replacement for several weeks; the same person later posted that it came back after the next renewal. That is one person's account, not X policy, but it matches the pattern that these grants are tied to a cycle and do not accumulate.

Why this matters for searchers. In our study of 618 public posts about X API credits, 25.1% (155 posts) mentioned Grok Bot, @bot, SuperGrok or Premium. For our Grok Bot page we measured what typical Grok Bot X tasks read and what they cost; read it if your credits come from a subscription rather than a card.

We searched X for posts about X API vouchers, free credits and credits depleted, and the X developer forum for topics on the same themes, then sorted both by transparent keyword rules. Everything below is an aggregate; no individual is profiled.

On X: 618 unique posts. Five searches returned 618 unique posts after dropping retweets (546 of them from 2026). The largest themes were Grok Bot or X Premium (25.1%) and price or pay-per-use cost (22.8%). Free-credit amounts came up in 9.4%; "not received" or "missing" in 4.9%; out of credits or 402 in 4.9%; the literal word "voucher" in only 4.0%.

Inside the voucher talk. Of the 71 posts that mention a voucher or a free-credit amount directly, 21.1% talk about expiry or a zeroed balance, 15.5% say the credit never arrived, and 11.3% ask someone (often @XDevelopers) to send one. 19.6% of all posts mention @XDevelopers or @API.

On devcommunity.x.com: 199 topics since the pilot. Searches for voucher, free credits, credits depleted and $20 credit returned 213 unique topics; 199 were opened after the pay-per-use pilot began in October 2025, and 65 of those have a title that matches one of the credit themes below. The rest are other topics the same searches surfaced.

Reading it. The single biggest credit theme on the forum is not a missing voucher but a 402 or credits-depleted error (15 topics), often with credits still showing in the console. The $10 migration voucher and the $20 / $70 incentives each produced 13 and 13 complaint topics, and another 13 topics simply ask X for free credits for a project (hackathons, non-profits, public-interest apps). X's documented route for free scaled access is the Public Utility App classification, not a voucher request.

A voucher is only worth what it buys. On X's rate card (docs.x.com/x-api/getting-started/pricing, read this session), a post read costs $0.005, a user read $0.010, a follower or following read $0.010, and creating a post $0.015 ($0.20 with a URL). Pay-per-usage is capped at 3 million post reads a month; above that X points to Enterprise. Requests for the same resource are deduplicated within a 24-hour UTC window.

The same budget on TwitterAPI.io. Tweet endpoints cost 15 credits per tweet returned, $0.15 per 1,000 tweets, with a minimum of 15 credits per request ($0.00015 when a search returns nothing). Profiles cost $0.18 per 1,000. $1 is 100,000 credits, and purchased credits never expire. Per 1,000 posts that is $5 on X's pay-per-use rate card against $0.15 here, about 33x; the X figure is X's own published rate, ours is our published rate.

Our free credits, stated exactly. New TwitterAPI.io accounts that pass the automatic bot check get up to $1 of free credits (at most 100,000 credits, no card, one per person or network, expiring after 31 days). That is up to about 6,600 tweets at 15 credits each, enough to run the script below many times. Reads need no X account and no developer approval. Before the first payment the rate limit is 0.2 requests per second; it rises to 20 once paid.

When the official API is still the right call. If you need to act as your own users through OAuth, read owned data at X's Owned Reads rate of $0.001 per resource, or you are a Public Utility App, X's own API and its credits fit. For reading public posts, profiles and followers at volume, a third-party read API costs a fraction of X's rate card. TwitterAPI.io also has write endpoints (post, like, follow, DM) that act through a logged-in X account at 60 credits ($0.0006) per call after a $0.10 login; that call acts as that account, so X can rate-limit, lock or suspend it, keep a human pace, the session may need a re-login, and each HTTP 200 call is billed.

A budget guard that stops before $0. The pattern behind most voucher complaints is the same on any credit-based API: the balance silently drains, the next call fails, and the job dies halfway. The script in the code block at the end of this page avoids that on TwitterAPI.io. It reads the remaining balance with /oapi/my/info (field recharge_credits), estimates the cost of each page before requesting it (15 credits per tweet, 20 tweets per full page, 15-credit minimum), stops cleanly before a floor you set, and prints what the same pull would have cost on X's $0.005 rate card.

Why estimate before the call. A full /twitter/tweet/advanced_search page returns up to 20 tweets, so the worst case is 300 credits ($0.003). Checking that the balance covers one more page before requesting it means the job ends with a clear message instead of an error mid-run.

On the official API, the equivalent safety nets are the spending limit per billing cycle and turning off auto-recharge if you only want to spend the free credits; remember that since May 21, 2026 auto-recharge also fires when a voucher balance runs out.

Question. When developers post publicly about X API vouchers and free X API credits, what are they talking about, and what did X's official accounts say about each program?

Sources and queries. Five /twitter/tweet/advanced_search queries (Latest) on TwitterAPI.io: voucher with X API terms; X API with free credits or a $20 credit; X API with out of credits or credits depleted; "x api" credits; and replies to @XDevelopers or @API about credits, vouchers, billing or refunds. Plus the timelines of the organization accounts @XDevelopers and @API, a search of their posts for voucher or credit, posts by two X staff accounts about credits, and the public search of devcommunity.x.com for voucher, free credits, free credit, credits depleted and $20 credit (topic titles only).

Window and sample. Whatever each search returned newest-first when we collected it, in 2026: 618 unique posts after removing retweets (most from 2026, a few back to 2023 for the broad "x api" credits query), and 213 forum topics, of which 199 were opened after the pay-per-use pilot began. 69 API requests in total, about $0.17 of credits.

Method. Themes come from transparent keyword rules in data/studies/x-api-voucher/analyze.py; a post or topic can match more than one theme, so shares do not add to 100%. Program facts come from docs.x.com pages and official posts, not from the counts.

What the sample cannot show. Search returns what the index surfaces, not every post; keyword rules miss sarcasm and posts in other languages; forum titles are not outcomes, so a topic counted as "missing $20" may have been resolved later. The counts show what people talk about, not how often X's billing actually fails.

Privacy. Aggregates only. Search results contain private individuals, so raw pages were kept out of the repository; the committed sample holds de-identified rows (theme flags, language, engagement counts) with no ids, text or handles. Only X's official accounts and X staff speaking publicly about these programs are named.