shipapis
StarSubmit an APISubmit API

IBGE vs PostalCodes

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

APIIBGENEW—PostalCodesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBGE vs PostalCodes: common questions

Which is more reliable, IBGE or PostalCodes?

On our scheduled checks, PostalCodes leads on measured uptime — IBGE at —% versus PostalCodes 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 IBGE and PostalCodes need an API key?

Neither needs a paid key — IBGE 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 IBGE and PostalCodes from the browser?

Only IBGE 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 IBGE and PostalCodes free for commercial use?

IBGE 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.