Battle.net vs XIVAPI

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1024578
P95 · ms31731451
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified; game content © Square Enix
Free tierFree tier — key may be requiredFree; optional free key raises limits
Rate limitUnpublishedRate-limited; higher limits with a free key (see docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Battle.net vs XIVAPI: common questions

Which is more reliable, Battle.net or XIVAPI?

Both are neck-and-neck — Battle.net and XIVAPI each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Battle.net or XIVAPI?

XIVAPI has the lower median latency in our checks — Battle.net responds in 1024 ms versus XIVAPI at 578 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 Battle.net and XIVAPI need an API key?

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

Can I call Battle.net and XIVAPI from the browser?

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

Are Battle.net and XIVAPI free for commercial use?

Battle.net has unclear commercial terms, and XIVAPI 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.