shipapis
StarSubmit an APISubmit API

IFTTT vs OpenQR

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

APIIFTTTNEW—OpenQRNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IFTTT vs OpenQR: common questions

Which is more reliable, IFTTT or OpenQR?

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

IFTTT needs no key, while OpenQR requires a free API key. If you want to start calling without signup, reach for IFTTT first.

Can I call IFTTT and OpenQR from the browser?

Only OpenQR 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 IFTTT and OpenQR free for commercial use?

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