Teach the API. Earn credits back.
Publish an honest tutorial, build log, or video about how you use TwitterAPI.io — on Dev.to, Reddit, X, YouTube, Qiita, Zenn, Hashnode, your own blog, or anywhere else developers hang out — and we'll send credits back. If people sign up and later pay through your share code, you can also earn affiliate commission on their payments, under the affiliate program terms.
How it works
Publish
Write a tutorial, record a walkthrough, or post a build log. Put your referral link or share code in the body of the post so we can verify the author.
Submit
From your dashboard, paste the URL and check the disclosure box. We detect the platform and tier automatically from the URL — no form to fill out. Our auto-review runs within a few hours and most submissions get decided within 3 business days.
Earn
Approved posts enter a short hold — 3 days for Tier A, 7 days for Tier B/C — while we confirm the post is still live. After the final check, credits unlock in your TwitterAPI.io balance and you have 30 days to spend them on any API endpoint. If someone signs up through your share code and later pays, you can also earn affiliate commission on their payments, under the affiliate program terms.
Reward tiers
The tier is set by where you publish: X, Reddit, LinkedIn, Bluesky and Mastodon posts are Tier A; Dev.to, Medium, Hashnode, Substack, Qiita, Zenn, note.com and personal blogs are Tier B; YouTube, Hacker News and GitHub are Tier C. You don't pick — the submission form reads the URL.
Short post
- Short public post about a specific API use case
- Your referral link or share code in the body of the post
- Published on X, Reddit, LinkedIn, Bluesky, or Mastodon
- — X thread (3+ posts)
- — LinkedIn status
- — Reddit post in a relevant subreddit
Long-form tutorial
- 600+ words (1,200+ characters for CJK) covering a problem → solution
- Ideally one worked example someone else could run
- Published on Dev.to, Medium, Hashnode, Substack, Qiita, Zenn, note.com, or your own blog
- — "How I built a trend-hunter bot with TwitterAPI.io"
- — "Switching from Twitter v2 to TwitterAPI.io — a code-level diff"
Video / HN / big GitHub
- YouTube video 3+ minutes actually showing the API working, OR
- Hacker News post with 5+ comments, OR
- Public GitHub repo with 20+ stars using the API
- — Full-build YouTube tutorial
- — Show HN with real traction
- — An open-source project that depends on us
Monthly cap: up to $200 of credits per account, across all tiers and platforms. One reward per platform per account, ever.
Accepted platforms
We accept any public, indexable platform. Platforms we see most often:
Platform not listed? Submit anyway — we add platforms as submissions come in.
Fair play
The rules below protect the program, the platforms, and your account.
Disclose that it's a sponsored mention
FTC in the US, Reddit site rules, and most platforms require you to say the post is sponsored or that you receive something in return. Our submission form has a checkbox you must sign off on. We don't accept submissions without disclosure.
We never buy dofollow links
The reward is for the content, not for a link attribute. Whatever the platform defaults to (nofollow, UGC, sponsored) is fine. We don't ask for and won't pay extra for a dofollow link. This keeps everyone out of Google's link-scheme policy.
One reward per platform, ever — up to $200/mo total
Your first approved X post earns a reward; a second X post later doesn't. Same for every other platform. You can cross-post the same article to Dev.to, Medium, Hashnode, Qiita, Zenn and your own blog — each one is its own platform and earns separately. Across all platforms, a single account can earn at most $200 of credits per calendar month.
Credits unlock after a short hold, then 30 days to spend
When your post is approved it enters a hold — 3 days for short posts (Tier A), 7 days for long-form, video, GitHub and Hacker News (Tier B/C) — while we confirm it's still live. After the hold, credits unlock in your TwitterAPI.io balance and you have 30 days to spend them. If the post is removed, made private, or no longer contains your referral link or share code during the hold, the reward is cancelled before any credits are released. During the 30-day usage window we recheck at day 7 and day 21; if the post is gone or no longer carries your referral link or share code, the unused portion is clawed back — credits you've already spent stay yours.
Honest only — plagiarism disqualifies
If you copy someone else's post and change the share code, we revoke the reward and may close your eligibility. Keep it in your own voice; even a short, honest post beats a long, laundered one.
Not every platform is in scope
Review sites like Trustpilot and G2 forbid any form of incentivized review — we don't accept submissions from there. Hidden-link or cloaked-redirect posts don't qualify either. If you're unsure, submit anyway and we'll say so when we review.
FAQ
- What counts as an "accepted platform"?
- Any public web page we can fetch. The ones we auto-review today: X, Reddit, Dev.to, Bluesky, GitHub, Hacker News, YouTube and the big Mastodon instances. Everything else — Medium, LinkedIn, Substack, Hashnode, Qiita, Zenn, note.com, personal blogs — still works; it goes through our manual queue instead of the auto-review. Submit anything public and we'll handle it.
- How do you confirm the post is really mine?
- Your submission has to contain either your referral link or your 8-character share code (the same code as your affiliate program) somewhere in the body of the post — not just in the comments. Our auto-review fetches the public page and checks. The first time a platform account is approved we bind it to your account; the next time anyone else submits a post from that platform account it's flagged for human review.
- Can I write a critical review?
- Yes — in fact, we'd rather have an honest piece that lists what doesn't work than a glossy puff piece that reads like an ad. The quality bar is "would another developer learn something?", not "is TwitterAPI.io the best?". Dishonest praise is worse for us than honest critique.
- When do I actually see the credits?
- After a short hold while we confirm the post is still live — 3 days for short posts (Tier A), 7 days for long-form, video, GitHub and Hacker News (Tier B/C). The final check at the end of the hold runs automatically; if the post is still up and still carries your referral link or share code, the credits unlock in your TwitterAPI.io balance and you have 30 days to spend them. Posts removed during the hold are cancelled before any credits are released.
- Can I cross-post the same article to multiple platforms?
- Yes, and it's encouraged. The same tutorial on Dev.to, Hashnode, Qiita and your own blog counts as four separate platforms, so you can earn up to four Tier-B rewards from one piece of writing. The only limits are: one reward per platform (ever), and $200/month across all platforms.
- Can I submit old posts I wrote before this program existed?
- Yes, if they're still live and the disclosure is already visible, or you add it. We approve older posts too — the reward is for value delivered, not for a publish date.
- Do I also earn affiliate commission if someone signs up through my link?
- Yes — on top of the Community Rewards credits. Your share code is the same one as your affiliate link. If someone signs up through your referral and later pays, you can also earn affiliate commission on their payments, under the affiliate program terms (12-month window, per-payer cap and self-referral rules apply). The Community Rewards credit for the post is separate from any affiliate commission on payments. See the Affiliate program page for the full rules.
- Do credits expire?
- Yes. After they unlock (3 days after approval for Tier A, 7 days for Tier B/C), Community Rewards credits expire 30 days later. Spend them on any API endpoint within those 30 days. They can't be converted to cash.
Ready to teach the API?
Publish, then submit. Reviews are automatic where we can read the post, and a person looks at everything else — if something's unclear, we'll say so when we review.