shipapis
StarSubmit an APISubmit API

IFTTT vs OpenQR

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

APIIFTTTHEALTHY92OpenQRHEALTHY80
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms6821125
P95 · ms12622851
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?

Both are neck-and-neck — IFTTT and OpenQR 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, IFTTT or OpenQR?

IFTTT has the lower median latency in our checks — IFTTT responds in 682 ms versus OpenQR at 1125 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 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.