shipapis
StarSubmit an APISubmit API

BulkSMS JSON REST API vs LectServe

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

APIBulkSMS JSON REST APINEW—LectServeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesno
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

BulkSMS JSON REST API vs LectServe: common questions

Which is more reliable, BulkSMS JSON REST API or LectServe?

On our scheduled checks, LectServe leads on measured uptime — BulkSMS JSON REST API at —% versus LectServe 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 BulkSMS JSON REST API and LectServe need an API key?

LectServe needs no key, while BulkSMS JSON REST API requires a free API key. If you want to start calling without signup, reach for LectServe first.

Can I call BulkSMS JSON REST API and LectServe from the browser?

Neither sends browser-friendly CORS headers reliably, so call BulkSMS JSON REST API and LectServe from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are BulkSMS JSON REST API and LectServe free for commercial use?

BulkSMS JSON REST API has unclear commercial terms, and LectServe 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.