shipapis
StarSubmit an APISubmit API

API Reference - Ideal Postcodes vs Geocodify.com

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

APIAPI Reference - Ideal PostcodesNEW—Geocodify.comREACHABLE—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesyes
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

API Reference - Ideal Postcodes vs Geocodify.com: common questions

Which is more reliable, API Reference - Ideal Postcodes or Geocodify.com?

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

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

Can I call API Reference - Ideal Postcodes and Geocodify.com from the browser?

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

API Reference - Ideal Postcodes has unclear commercial terms, and Geocodify.com 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.