How do you earn TwitterAPI.io credits by writing about the API?

Sign in and open Dashboard → Community Rewards (/dashboard/community-rewards). The section "Your proof-of-authorship credentials" shows two values with copy buttons: your share code (8 characters) and your referral link (twitterapi.io/?ref=<your code>). Either one works. It is the same code as your affiliate link, so you don't need to set anything up separately.

The code is how the review knows the post is yours. The auto-review fetches the public page and looks for the code or the link in the body. The first time a platform account is approved, it is bound to your TwitterAPI.io account; if anyone else later submits a post from that platform account, it goes to a person for review.

Where to put it: in the text of the post itself. A code that only appears in a comment, a reply or a pinned follow-up does not count. On X, put it in the post whose URL you submit.

You don't choose a tier. The form reads the URL and sets it from the platform. That makes the plan mostly a question of where the post will be useful to readers.

Two limits shape the plan. Each platform pays once per account, ever: a second X post later earns nothing. And one account can receive at most $200 of credits per calendar month across all platforms.

Review sites are out. Trustpilot, G2 and similar sites forbid incentivized reviews, so they are not accepted. Platforms that are not listed can still be submitted; the reviewer will tell you if one doesn't qualify.

Write in your own voice about something you actually built or measured. A post that is mostly links with little text of its own is likely to be held for a person to look at, and a copied post with a swapped share code loses the reward and can end eligibility.

Disclosure is required. The submission form asks you to confirm that the post says you receive credits in return, in whatever form the platform expects (an FTC-style disclosure for US readers, Reddit's self-promotion rules, a platform's own sponsored tag). One plain sentence is enough if readers can't miss it: the FTC's influencer guide warns that a disclosure only at the end of a post, on a profile page or behind a "more" click is likely to be missed, so put it near the top, next to the first mention. For example:

Example disclosure line: "Disclosure: I receive TwitterAPI.io credits for this post through their Community Rewards program. My referral link: twitterapi.io/?ref=AB12CD34"

Links: the program never pays for a dofollow link and never asks for one. Whatever the platform does with links by default (nofollow, UGC, sponsored) is fine.

What to write about is up to you. Topics that tend to help readers are a working script with its output, a cost comparison you measured, a migration from another client, or an honest list of what didn't work. If you need a starting point, the Claude + Twitter API guide and the Twitter API pricing breakdown show the level of detail readers find useful.

In the same dashboard page, paste one public post URL into Post URL, write a short summary (at least 30 characters) under "What's in the post?", tick the disclosure box and press Submit for review. One URL per submission.

Medium and LinkedIn: these pages can't be fetched automatically, so paste the full text of the post into the summary box. The check then runs against that text.

Errors you might see: "platform already used" means you already have a reward on that platform; "duplicate URL" means this URL or a variant of it was already submitted; a non-public URL (an internal address, an IP, a private page) is rejected.

What happens next: the auto-review runs every few hours and checks the body for your code and the tier gates (video length, GitHub stars, Hacker News comments). Personal blogs, Medium, LinkedIn, Hashnode, Qiita, Zenn and Substack go to a short manual review. You get an email when it's decided, within 3 business days.

An approved post doesn't pay immediately. It enters a hold of 3 days for Tier A and 7 days for Tier B and C, while the post is confirmed to still be live. A final automatic check runs at the end of the hold. If the post is still up and still carries your code or link, the credits unlock in your balance.

From the unlock you have 30 days to spend them on any endpoint. During those 30 days the post is checked again on day 7 and day 21. If it has been removed, made private, or the code is gone, the unused part of the reward is taken back; credits you already spent stay yours. If the post disappears during the hold, the reward is cancelled before anything is released.

Reward credits can't be converted to cash. If people sign up through your link and later pay, that is a separate affiliate commission under the affiliate program terms (12-month window, per-payer cap and self-referral rules).

Our made-up developer wrote one tutorial, "A keyword alert for X in 40 lines of Python", published it on their own blog, cross-posted it to Dev.to and Hashnode, and wrote a three-post X thread that links to it. Each URL is submitted separately.

$65 is under the $200 monthly cap, so all four pay in full. Next month the same four platforms pay nothing more for this account; a YouTube walkthrough of the same build would be new (Tier C, $30), and so would the code as a GitHub repo once it passes 20 stars.

What $65 of credits buys: reads cost $0.15 per 1,000 tweets returned on TwitterAPI.io, so $65 covers about 433,000 tweets. The official X API pay-per-usage rate card (docs.x.com/x-api/getting-started/pricing, as of 2026) lists Posts: Read at $0.005 per resource for reading other accounts' posts, where the same $65 reads 13,000 posts.

If the code goes missing: suppose the Dev.to version is edited on day 10 after unlock and the referral line is cut. The day-21 check finds no code, and whatever is left of that $20 is taken back. That is why the next step exists.

The script below checks each post you submitted the way the review does: is it still public, and does the body still contain your share code or referral link? X posts are read through GET /twitter/tweets (the text plus the expanded entities.urls, because X shortens links to t.co); other platforms are fetched as plain web pages. Run it before you submit and again around day 7 and day 21 after the unlock.

Cost: each X post checked is one tweet returned, 15 credits ($0.00015). Checking four posts three times costs less than a cent; web pages cost nothing.

Public: the post opens in a private browser window without signing in.

Code in the body: your share code or referral link is in the post text, not a comment (the script above prints OK).

Disclosure: one sentence says you receive TwitterAPI.io credits for the post.

Your own words: something you built, measured or ran into, not a rewrite of someone else's post or of our docs.

Tier gate met: 600+ words (1,200+ CJK characters) for Tier B; 3+ minutes of the API actually running for YouTube; 5+ comments for Hacker News; 20+ stars for GitHub.

New platform: you haven't been rewarded on this platform before.

Kept up: you plan to leave the post and the code in place until the credits are spent.