shipapis
StarSubmit an APISubmit API

TwitterApi.IO vs Disify

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

APITwitterApi.IOON SCHEDULE—DisifyNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

TwitterApi.IO vs Disify: common questions

Which is more reliable, TwitterApi.IO or Disify?

Only Disify is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do TwitterApi.IO and Disify need an API key?

Disify needs no key, while TwitterApi.IO requires a free API key. If you want to start calling without signup, reach for Disify first.

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

Only Disify 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 Disify free for commercial use?

TwitterApi.IO has unclear commercial terms, and Disify 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.