shipapis
StarSubmit an APISubmit API

Battle.net vs TCGApi

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

APIBattle.netHEALTHY85TCGApiHEALTHY100
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms102466
P95 · ms3173243
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — API key may be required for production
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Battle.net vs TCGApi: common questions

Which is more reliable, Battle.net or TCGApi?

Both are neck-and-neck — Battle.net and TCGApi 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 TCGApi?

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

Both ask you to authenticate — Battle.net uses an API key and TCGApi uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

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

Only TCGApi 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 TCGApi free for commercial use?

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