DummyJSON vs FakeStoreAPI

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree — no key required
Rate limit100 req/window · 99 remaining · resets 1783510243Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DummyJSON vs FakeStoreAPI: common questions

Which is more reliable, DummyJSON or FakeStoreAPI?

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

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

Can I call DummyJSON and FakeStoreAPI from the browser?

Yes — both DummyJSON and FakeStoreAPI 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 DummyJSON and FakeStoreAPI free for commercial use?

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