shipapis
StarSubmit an APISubmit API

ClickSend REST API v3 vs Postcodes.io

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

APIClickSend REST API v3NEW—Postcodes.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedService MIT-licensed; postcode data license unverified
Free tierFree tier — API key requiredFree — no key required
Rate limit6000 req/window · 5999 remaining · resets 1Unpublished (no key; fair use)
In directory since2026-07-052026-07-05
operationalpartialdownno data

ClickSend REST API v3 vs Postcodes.io: common questions

Which is more reliable, ClickSend REST API v3 or Postcodes.io?

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

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

Can I call ClickSend REST API v3 and Postcodes.io from the browser?

Yes — both ClickSend REST API v3 and Postcodes.io 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 ClickSend REST API v3 and Postcodes.io free for commercial use?

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