shipapis
StarSubmit an APISubmit API

OpenQR vs ParlayAPI

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

APIOpenQRHEALTHY75ParlayAPIREACHABLE88
Uptime · 30d
Uptime · 90d100%87.5%
Uptime · 30d100%87.5%
P50 · ms2356211
P95 · ms49871536
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree tier — key may be required
Rate limitUnpublished
In directory since2026-07-052026-10-04
operationalpartialdownno data

OpenQR vs ParlayAPI: common questions

Which is more reliable, OpenQR or ParlayAPI?

On our scheduled checks, OpenQR leads on measured uptime — OpenQR at 100% versus ParlayAPI at 87.5% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, OpenQR or ParlayAPI?

ParlayAPI has the lower median latency in our checks — OpenQR responds in 2356 ms versus ParlayAPI at 211 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 OpenQR and ParlayAPI need an API key?

Both ask you to authenticate — OpenQR uses an API key and ParlayAPI uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call OpenQR and ParlayAPI from the browser?

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

Are OpenQR and ParlayAPI free for commercial use?

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