shipapis
StarSubmit an APISubmit API

IPLocate vs SnapAPI

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

APIIPLocateNEW—SnapAPINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPLocate vs SnapAPI: common questions

Which is more reliable, IPLocate or SnapAPI?

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

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

Can I call IPLocate and SnapAPI from the browser?

Yes — both IPLocate and SnapAPI 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 IPLocate and SnapAPI free for commercial use?

IPLocate has unclear commercial terms, and SnapAPI 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.