Harry Potter API vs Shoof Aflam

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Harry Potter API vs Shoof Aflam: common questions

Which is more reliable, Harry Potter API or Shoof Aflam?

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

Neither needs a paid key — Harry Potter API is callable with no signup, and Shoof Aflam is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Harry Potter API and Shoof Aflam from the browser?

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

Are Harry Potter API and Shoof Aflam free for commercial use?

Harry Potter API has unclear commercial terms, and Shoof Aflam 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.