shipapis
StarSubmit an APISubmit API

DummyJSON vs OOPSpam

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

APIDummyJSONHEALTHY100OOPSpamHEALTHY99
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms91217
P95 · ms1929434
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?

Both are neck-and-neck — DummyJSON and OOPSpam each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, DummyJSON or OOPSpam?

DummyJSON has the lower median latency in our checks — DummyJSON responds in 91 ms versus OOPSpam at 217 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 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.