Bitbucket Cloud API vs Web of Science API Expanded

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limit60, 60;w=3600 req/window · 59 remaining · resets 2635Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bitbucket Cloud API vs Web of Science API Expanded: common questions

Which is more reliable, Bitbucket Cloud API or Web of Science API Expanded?

On our scheduled checks, Web of Science API Expanded leads on measured uptime — Bitbucket Cloud API at —% versus Web of Science API Expanded 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 Bitbucket Cloud API and Web of Science API Expanded need an API key?

Both ask you to authenticate — Bitbucket Cloud API uses an API key and Web of Science API Expanded 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 Bitbucket Cloud API and Web of Science API Expanded from the browser?

Only Bitbucket Cloud API is browser-friendly — it returns CORS headers over HTTPS. Web of Science API Expanded needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Bitbucket Cloud API and Web of Science API Expanded free for commercial use?

Bitbucket Cloud API has unclear commercial terms, and Web of Science API Expanded 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.