OpenSanctions vs SnapshotAPI

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

Uptime · 30d
Uptime · 90d100%6.9%
Uptime · 30d100%0.0%
P50 · ms387396
P95 · ms4183547
AuthnoneapiKey
CORSyesno
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

OpenSanctions vs SnapshotAPI: common questions

Which is more reliable, OpenSanctions or SnapshotAPI?

On our scheduled checks, OpenSanctions leads on measured uptime — OpenSanctions at 100% versus SnapshotAPI at 6.9% 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, OpenSanctions or SnapshotAPI?

OpenSanctions has the lower median latency in our checks — OpenSanctions responds in 387 ms versus SnapshotAPI at 396 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 OpenSanctions and SnapshotAPI need an API key?

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

Can I call OpenSanctions and SnapshotAPI from the browser?

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

Are OpenSanctions and SnapshotAPI free for commercial use?

OpenSanctions has unclear commercial terms, and SnapshotAPI 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.