shipapis
StarSubmit an APISubmit API

GeoApi vs PostalCodes

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

APIGeoApiNEW—PostalCodesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseLicence Ouverte (Etalab; INSEE/IGN data)Unverified
Free tierFree, no API keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoApi vs PostalCodes: common questions

Which is more reliable, GeoApi or PostalCodes?

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

Neither needs a paid key — GeoApi is callable with no signup, and PostalCodes is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call GeoApi and PostalCodes from the browser?

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

Are GeoApi and PostalCodes free for commercial use?

GeoApi allows commercial use on its free tier, and PostalCodes 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.