API Reference - Ideal Postcodes vs PostalCodes
Same instrument, two spec sheets — measured, not claimed.
API Reference - Ideal Postcodes vs PostalCodes: common questions
Which is more reliable, API Reference - Ideal Postcodes or PostalCodes?
On our scheduled checks, API Reference - Ideal Postcodes leads on measured uptime — API Reference - Ideal Postcodes at 100% versus PostalCodes at 99.02% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Which is faster, API Reference - Ideal Postcodes or PostalCodes?
API Reference - Ideal Postcodes has the lower median latency in our checks — API Reference - Ideal Postcodes responds in 154 ms versus PostalCodes at 1030 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.
Do API Reference - Ideal Postcodes and PostalCodes need an API key?
Neither needs a paid key — API Reference - Ideal Postcodes 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 API Reference - Ideal Postcodes and PostalCodes from the browser?
Only API Reference - Ideal Postcodes 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 API Reference - Ideal Postcodes and PostalCodes free for commercial use?
API Reference - Ideal Postcodes has unclear commercial terms, 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.