shipapis
StarSubmit an APISubmit API

API Reference - Ideal Postcodes vs GeoJS

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

APIAPI Reference - Ideal PostcodesUNMONITORED—GeoJSNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree, no API key required
Rate limitUnpublishedUnpublished (no enforced limit stated)
In directory since2026-07-052026-07-05
operationalpartialdownno data

API Reference - Ideal Postcodes vs GeoJS: common questions

Which is more reliable, API Reference - Ideal Postcodes or GeoJS?

Only GeoJS is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do API Reference - Ideal Postcodes and GeoJS need an API key?

Neither needs a paid key — API Reference - Ideal Postcodes 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 API Reference - Ideal Postcodes and GeoJS from the browser?

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

API Reference - Ideal Postcodes 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.