shipapis
StarSubmit an APISubmit API

Geocodify.com vs Postcodes.io

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

APIGeocodify.comREACHABLE—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 limitUnpublishedUnpublished (no key; fair use)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Geocodify.com vs Postcodes.io: common questions

Which is more reliable, Geocodify.com or Postcodes.io?

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

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

Can I call Geocodify.com and Postcodes.io from the browser?

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

Geocodify.com 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.