shipapis
StarSubmit an APISubmit API

API Reference - Ideal Postcodes vs ipapi.co

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

APIAPI Reference - Ideal PostcodesNEW—ipapi.coNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — quota not published; returns 429 when exceeded
Rate limitUnpublishedUnpublished (429 Quota exceeded)
In directory since2026-07-052026-07-05
operationalpartialdownno data

API Reference - Ideal Postcodes vs ipapi.co: common questions

Which is more reliable, API Reference - Ideal Postcodes or ipapi.co?

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

Neither needs a paid key — API Reference - Ideal Postcodes is callable with no signup, and ipapi.co is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call API Reference - Ideal Postcodes and ipapi.co from the browser?

Only API Reference - Ideal Postcodes is browser-friendly — it returns CORS headers over HTTPS. ipapi.co needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are API Reference - Ideal Postcodes and ipapi.co free for commercial use?

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