shipapis
StarSubmit an APISubmit API

DummyJSON vs IFTTT

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

APIDummyJSONNEW—IFTTTNEW—
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 1783510243Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DummyJSON vs IFTTT: common questions

Which is more reliable, DummyJSON or IFTTT?

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

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

Can I call DummyJSON and IFTTT from the browser?

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

Are DummyJSON and IFTTT free for commercial use?

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