shipapis
StarSubmit an APISubmit API

Exchangerate.dev vs IBAN Validation API

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

APIExchangerate.devNEW—IBAN Validation APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit12 req/window · 11 remaining · resets 1783515720Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Exchangerate.dev vs IBAN Validation API: common questions

Which is more reliable, Exchangerate.dev or IBAN Validation API?

On our scheduled checks, IBAN Validation API leads on measured uptime — Exchangerate.dev at —% versus IBAN Validation API 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 Exchangerate.dev and IBAN Validation API need an API key?

Neither needs a paid key — Exchangerate.dev is callable with no signup, and IBAN Validation API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Exchangerate.dev and IBAN Validation API from the browser?

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

Are Exchangerate.dev and IBAN Validation API free for commercial use?

Exchangerate.dev has unclear commercial terms, and IBAN Validation 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.