shipapis
StarSubmit an APISubmit API

positionstack vs Postcodes.io

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

APIpositionstackHEALTHY93Postcodes.ioHEALTHY100
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms45533
P95 · ms3328328
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedService MIT-licensed; postcode data license unverified
Free tierFree tier — key may be requiredFree — no key required
Rate limitUnpublishedUnpublished (no key; fair use)
In directory since2026-07-052026-07-05
operationalpartialdownno data

positionstack vs Postcodes.io: common questions

Which is more reliable, positionstack or Postcodes.io?

Both are neck-and-neck — positionstack and Postcodes.io each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, positionstack or Postcodes.io?

Postcodes.io has the lower median latency in our checks — positionstack responds in 455 ms versus Postcodes.io at 33 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 positionstack and Postcodes.io need an API key?

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

Can I call positionstack and Postcodes.io from the browser?

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

Are positionstack and Postcodes.io free for commercial use?

positionstack has unclear commercial terms, and Postcodes.io 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.