httpSMS vs OnSched Consumer API
Same instrument, two spec sheets — measured, not claimed.
httpSMS vs OnSched Consumer API: common questions
Which is more reliable, httpSMS or OnSched Consumer API?
On our scheduled checks, OnSched Consumer API leads on measured uptime — httpSMS at —% versus OnSched Consumer API 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 OnSched Consumer API need an API key?
Both ask you to authenticate — httpSMS uses an API key and OnSched Consumer API 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 OnSched Consumer API from the browser?
Yes — both httpSMS and OnSched Consumer API 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 OnSched Consumer API free for commercial use?
httpSMS has unclear commercial terms, and OnSched Consumer API 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.