ClickSend REST API v3 vs ISO 3166-2 API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limit6000 req/window · 5999 remaining · resets 1Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ClickSend REST API v3 vs ISO 3166-2 API: common questions

Which is more reliable, ClickSend REST API v3 or ISO 3166-2 API?

On our scheduled checks, ISO 3166-2 API leads on measured uptime — ClickSend REST API v3 at —% versus ISO 3166-2 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 ClickSend REST API v3 and ISO 3166-2 API need an API key?

ISO 3166-2 API needs no key, while ClickSend REST API v3 requires a free API key. If you want to start calling without signup, reach for ISO 3166-2 API first.

Can I call ClickSend REST API v3 and ISO 3166-2 API from the browser?

Only ClickSend REST API v3 is browser-friendly — it returns CORS headers over HTTPS. ISO 3166-2 API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are ClickSend REST API v3 and ISO 3166-2 API free for commercial use?

ClickSend REST API v3 has unclear commercial terms, and ISO 3166-2 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.