shipapis
StarSubmit an APISubmit API

httpSMS vs ScreenURL

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

APIhttpSMSDEAD0ScreenURLDEAD0
Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

httpSMS vs ScreenURL: common questions

Which is more reliable, httpSMS or ScreenURL?

Both are neck-and-neck — httpSMS and ScreenURL each measure 0.0% 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.

Do httpSMS and ScreenURL need an API key?

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

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

Are httpSMS and ScreenURL free for commercial use?

httpSMS has unclear commercial terms, and ScreenURL 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.