GLEIF LEI API vs OpenSanctions
Same instrument, two spec sheets — measured, not claimed.
GLEIF LEI API vs OpenSanctions: common questions
Which is more reliable, GLEIF LEI API or OpenSanctions?
On our scheduled checks, OpenSanctions leads on measured uptime — GLEIF LEI API at —% versus OpenSanctions 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 GLEIF LEI API and OpenSanctions need an API key?
Neither needs a paid key — GLEIF LEI API is callable with no signup, and OpenSanctions is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call GLEIF LEI API and OpenSanctions from the browser?
Yes — both GLEIF LEI API and OpenSanctions 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 GLEIF LEI API and OpenSanctions free for commercial use?
GLEIF LEI API has unclear commercial terms, and OpenSanctions 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.