DummyJSON vs OOPSpam

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree — limits not published
Rate limit100 req/window · 99 remaining · resets 17835102431000 req/window · 999 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

DummyJSON vs OOPSpam: common questions

Which is more reliable, DummyJSON or OOPSpam?

On our scheduled checks, OOPSpam leads on measured uptime — DummyJSON at —% versus OOPSpam 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 DummyJSON and OOPSpam need an API key?

Neither needs a paid key — DummyJSON is callable with no signup, and OOPSpam is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call DummyJSON and OOPSpam from the browser?

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

Are DummyJSON and OOPSpam free for commercial use?

DummyJSON has unclear commercial terms, and OOPSpam 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.