shipapis
StarSubmit an APISubmit API

ApogeoAPI vs PostalCodes

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

APIApogeoAPIDEAD0PostalCodesHEALTHY84
Uptime · 30d
Uptime · 90d0.0%99.02%
Uptime · 30d0.0%98.3%
P50 · ms—1030
P95 · ms—2594
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ApogeoAPI vs PostalCodes: common questions

Which is more reliable, ApogeoAPI or PostalCodes?

On our scheduled checks, PostalCodes leads on measured uptime — ApogeoAPI at 0.0% 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.

Do ApogeoAPI and PostalCodes need an API key?

PostalCodes needs no key, while ApogeoAPI requires a free API key. If you want to start calling without signup, reach for PostalCodes first.

Can I call ApogeoAPI and PostalCodes from the browser?

Neither sends browser-friendly CORS headers reliably, so call ApogeoAPI and PostalCodes from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are ApogeoAPI and PostalCodes free for commercial use?

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