shipapis
StarSubmit an APISubmit API

Bitbucket Cloud API vs Currents

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

APIBitbucket Cloud APINEW—CurrentsNEW—
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 — key may be 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 Currents: common questions

Which is more reliable, Bitbucket Cloud API or Currents?

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

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

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

Are Bitbucket Cloud API and Currents free for commercial use?

Bitbucket Cloud API has unclear commercial terms, and Currents 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.