shipapis
StarSubmit an APISubmit API

PostalCodes vs Smappee API

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

APIPostalCodesNEW—Smappee APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

PostalCodes vs Smappee API: common questions

Which is more reliable, PostalCodes or Smappee API?

On our scheduled checks, Smappee API leads on measured uptime — PostalCodes 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 PostalCodes and Smappee API need an API key?

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

Can I call PostalCodes and Smappee API from the browser?

Neither sends browser-friendly CORS headers reliably, so call PostalCodes and Smappee API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are PostalCodes and Smappee API free for commercial use?

PostalCodes 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.