shipapis
StarSubmit an APISubmit API

ClickSend REST API v3 vs IPWhois

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

APIClickSend REST API v3NEW—IPWhoisNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key may be required for production
Rate limit6000 req/window · 5999 remaining · resets 1Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ClickSend REST API v3 vs IPWhois: common questions

Which is more reliable, ClickSend REST API v3 or IPWhois?

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

Both ask you to authenticate — ClickSend REST API v3 uses an API key and IPWhois 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 ClickSend REST API v3 and IPWhois from the browser?

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

Are ClickSend REST API v3 and IPWhois free for commercial use?

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