shipapis
StarSubmit an APISubmit API

Postcodes.io vs Smappee API

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

APIPostcodes.ioNEW—Smappee APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseService MIT-licensed; postcode data license unverifiedUnverified
Free tierFree — no key requiredFree tier — API key required
Rate limitUnpublished (no key; fair use)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Postcodes.io vs Smappee API: common questions

Which is more reliable, Postcodes.io or Smappee API?

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

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

Can I call Postcodes.io and Smappee API from the browser?

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

Are Postcodes.io and Smappee API free for commercial use?

Postcodes.io has unclear commercial terms, and Smappee 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.