TwitterApi.IO
TwitterApi.IO — free tier with API key
TwitterApi.IO exposes a free-tier JSON API. Register for an API key if required; we verified a public or demo endpoint.
We probe without your API key. A 401/403 auth wall means the server is up — not a full health pass. Open provider docs ↗
On our probe schedule. Uptime charts appear after the first check lands.
GET https://api.twitterapi.io/backend/user/log_affiliate_click?referral_code=${refCode}&chrome_uid=${chromeUid}`
{
"status": "success"
}curl "https://api.twitterapi.io/backend/user/log_affiliate_click?referral_code=${refCode}&chrome_uid=${chromeUid}`"const res = await fetch("https://api.twitterapi.io/backend/user/log_affiliate_click?referral_code=${refCode}&chrome_uid=${chromeUid}`");
const data = await res.json();
console.log(data);import requests
res = requests.get("https://api.twitterapi.io/backend/user/log_affiliate_click?referral_code=${refCode}&chrome_uid=${chromeUid}`")
print(res.json())BROWSER CALLS BLOCKED (NO CORS/HTTPS) — USE THE CURL SNIPPET
/backend/user/log_affiliate_click?referral_code=${refCode}&chrome_uid=${chromeUid}`PROBEDTwitterApi.IO — free tier with API key
/backendBackend — documented GET route.
/backend/1Backend details by ID (example: 1).
/backend?limit=10Backend — documented GET route.
/backend/search?q=testSearch by query parameters.
/backend/user/log_affiliate_click?limit=5Single user profile.
We probe without your API key. A 401/403 auth wall means the server is up — not a full health pass. Export includes every documented route below.
Not tracked yet. Shape-change history starts once this API joins our probe schedule.
TwitterApi.IO: common questions
Is TwitterApi.IO free to use?
Yes — TwitterApi.IO is a free social & work API. Free tier: Free tier — API key required. Whether the free tier allows commercial use is unclear — check the provider docs.
Does TwitterApi.IO need an API key?
Yes — TwitterApi.IO needs a free API key, which you pass on each request. Rate limits: Unpublished.
Can I call TwitterApi.IO from the browser?
Not directly — TwitterApi.IO doesn't send browser-friendly CORS headers, so call it from a server or proxy instead. Copy the curl or Python snippet on this page to get started.
Is TwitterApi.IO up right now?
TwitterApi.IO is catalogued but not yet on our probe schedule, so we don't publish a live status for it. Check the provider's own status page or docs for its current state.