shipapis
StarSubmit an APISubmit API

LatLng vs Smappee API

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

APILatLngDYING68Smappee APIHEALTHY92
Uptime · 30d
Uptime · 90d59.4%100%
Uptime · 30d1.7%100%
P50 · ms617516
P95 · ms21711644
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit60 req/window · 59 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LatLng vs Smappee API: common questions

Which is more reliable, LatLng or Smappee API?

On our scheduled checks, Smappee API leads on measured uptime — LatLng at 59.4% versus Smappee API at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, LatLng or Smappee API?

Smappee API has the lower median latency in our checks — LatLng responds in 617 ms versus Smappee API at 516 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 LatLng and Smappee API need an API key?

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

Can I call LatLng and Smappee API from the browser?

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

Are LatLng and Smappee API free for commercial use?

LatLng has unclear commercial terms, and Smappee API 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.