shipapis
StarSubmit an APISubmit API

Tumblr vs TwitterApi.IO

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

APITumblrREACHABLE100TwitterApi.IOREACHABLE98
Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%96.7%
P50 · ms208242
P95 · ms11012593
AuthoauthapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierOAuth — some read routes may be publicFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Tumblr vs TwitterApi.IO: common questions

Which is more reliable, Tumblr or TwitterApi.IO?

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

Which is faster, Tumblr or TwitterApi.IO?

Tumblr has the lower median latency in our checks — Tumblr responds in 208 ms versus TwitterApi.IO at 242 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Tumblr and TwitterApi.IO need an API key?

Both ask you to authenticate — Tumblr uses OAuth and TwitterApi.IO 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 Tumblr and TwitterApi.IO from the browser?

Only Tumblr 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 Tumblr and TwitterApi.IO free for commercial use?

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