shipapis
StarSubmit an APISubmit API

X (Twitter) API vs xfetch

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

APIX (Twitter) APINEW—xfetchNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesyes
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

X (Twitter) API vs xfetch: common questions

Which is more reliable, X (Twitter) API or xfetch?

On our scheduled checks, xfetch leads on measured uptime — X (Twitter) API 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 X (Twitter) API and xfetch need an API key?

Both ask you to authenticate — X (Twitter) API 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 X (Twitter) API and xfetch from the browser?

Yes — both X (Twitter) API and xfetch send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are X (Twitter) API and xfetch free for commercial use?

X (Twitter) API 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.