shipapis
StarSubmit an APISubmit API

TwitterApi.IO

TwitterApi.IO — free tier with API key

💬 Social & WorkREACHABLEchecked 3h ago
AUTH APIKEYCORS ✗AGENT ✓HTTPS ✓COMMERCIAL ?

TwitterApi.IO exposes a free-tier JSON API. Register for an API key if required; we verified a public or demo endpoint.

98REACHABILITY SCORE ⓘ
Docs ↗
Status badge · for your READMEshipapis health badge: — · healthy
CHECK TIER · REACHABILITY

We probe without your API key. A 401/403 auth wall means the server is up — not a full health pass.

Uptime history
98.0%90d reachable
96.6%30d reachable
3hLast check · since JUL 8 · server OK
operationalpartialdownno data
Live response samplecaptured by our last successful check
GET https://api.twitterapi.io/backend/user/log_affiliate_click?referral_code=${refCode}&chrome_uid=${chromeUid}`

{
  "status": "success"
}
Call itcurl · fetch · python
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

Endpoints · 6ReachableFULL DOCS ↗
Auth wall reachable — GET /backend/user/log_affiliate_click?referral_code=${refCode}&chrome_uid=${chromeUid}` (key stripped)242 mschecked 3h ago
GET/backend/user/log_affiliate_click?referral_code=${refCode}&chrome_uid=${chromeUid}`PROBED

TwitterApi.IO — free tier with API key

GET/backend

Backend — documented GET route.

GET/backend/1

Backend details by ID (example: 1).

GET/backend?limit=10

Backend — documented GET route.

GET/backend/search?q=test

Search by query parameters.

GET/backend/user/log_affiliate_click?limit=5

Single user profile.

Machine-readable spec

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.

Response-shape history

Stable. No schema drift observed since monitoring began — the response shape has not changed under our checks.

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?

As of our last scheduled check, TwitterApi.IO is healthy with 98.0% uptime over 90 days and a 242 ms median response. We re-probe it every sweep — the status badge and uptime chart above always show the latest.