shipapis
StarSubmit an APISubmit API

httpSMS vs Logotypes

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

APIhttpSMSDEAD0LogotypesDEAD0
Uptime · 30d
Uptime · 90d0.0%47.8%
Uptime · 30d0.0%0.0%
P50 · ms—3645
P95 · ms—4993
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

httpSMS vs Logotypes: common questions

Which is more reliable, httpSMS or Logotypes?

On our scheduled checks, Logotypes leads on measured uptime — httpSMS at 0.0% versus Logotypes at 47.8% 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 Logotypes need an API key?

Logotypes needs no key, while httpSMS requires a free API key. If you want to start calling without signup, reach for Logotypes first.

Can I call httpSMS and Logotypes from the browser?

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

Are httpSMS and Logotypes free for commercial use?

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