LotteryData.io vs PotterDB

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (data derived from Harry Potter Fandom, CC BY-SA)
Free tierFree tier — API key requiredFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LotteryData.io vs PotterDB: common questions

Which is more reliable, LotteryData.io or PotterDB?

Only PotterDB is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do LotteryData.io and PotterDB need an API key?

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

Can I call LotteryData.io and PotterDB from the browser?

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

Are LotteryData.io and PotterDB free for commercial use?

LotteryData.io has unclear commercial terms, and PotterDB 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.