shipapis
StarSubmit an APISubmit API

httpSMS vs OpenQR

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

APIhttpSMSNEW—OpenQRNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

httpSMS vs OpenQR: common questions

Which is more reliable, httpSMS or OpenQR?

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

Both ask you to authenticate — httpSMS uses an API key and OpenQR 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 httpSMS and OpenQR from the browser?

Yes — both httpSMS and OpenQR send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are httpSMS and OpenQR free for commercial use?

httpSMS 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.