ParlayAPI vs QR & Barcode

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

Uptime · 30d
Uptime · 90d87.5%100%
Uptime · 30d87.5%100%
P50 · ms211511
P95 · ms15361231
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-10-042026-07-05
operationalpartialdownno data

ParlayAPI vs QR & Barcode: common questions

Which is more reliable, ParlayAPI or QR & Barcode?

On our scheduled checks, QR & Barcode leads on measured uptime — ParlayAPI at 87.5% versus QR & Barcode at 100% 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, ParlayAPI or QR & Barcode?

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

QR & Barcode needs no key, while ParlayAPI requires a free API key. If you want to start calling without signup, reach for QR & Barcode first.

Can I call ParlayAPI and QR & Barcode from the browser?

Only QR & Barcode 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 ParlayAPI and QR & Barcode free for commercial use?

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