shipapis
StarSubmit an APISubmit API

TwitterApi.IO vs xfetch

Same instrument, two spec sheets — measured, not claimed.

APITwitterApi.IOREACHABLE—xfetchNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

TwitterApi.IO vs xfetch: common questions

Which is more reliable, TwitterApi.IO or xfetch?

On our scheduled checks, xfetch leads on measured uptime — TwitterApi.IO at —% versus xfetch at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do TwitterApi.IO and xfetch need an API key?

Both ask you to authenticate — TwitterApi.IO uses an API key and xfetch uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call TwitterApi.IO and xfetch from the browser?

Only xfetch is browser-friendly — it returns CORS headers over HTTPS. TwitterApi.IO needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are TwitterApi.IO and xfetch free for commercial use?

TwitterApi.IO has unclear commercial terms, and xfetch has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.