shipapis
StarSubmit an APISubmit API

Postcodes.io vs GeoJS

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

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

Postcodes.io vs GeoJS: common questions

Which is more reliable, Postcodes.io or GeoJS?

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

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

Can I call Postcodes.io and GeoJS from the browser?

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

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