BulkSMS JSON REST API vs TimeZones iCal Library

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
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

BulkSMS JSON REST API vs TimeZones iCal Library: common questions

Which is more reliable, BulkSMS JSON REST API or TimeZones iCal Library?

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

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

Can I call BulkSMS JSON REST API and TimeZones iCal Library from the browser?

Only TimeZones iCal Library is browser-friendly — it returns CORS headers over HTTPS. BulkSMS JSON REST API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are BulkSMS JSON REST API and TimeZones iCal Library free for commercial use?

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