Bitbucket Pipelines · Rate Limits

Bitbucket Pipelines Rate Limits

Bitbucket Cloud applies hourly rate limits per app/installation/user and per IP, with a 1-hour sliding window. Pipelines also enforces concurrency caps (parallel-step limits) and a per-step build-time cap. The 1-hour API quota is observable through the X-RateLimit-* response headers and 429 carries a Retry-After hint.

Bitbucket Pipelines Rate Limits is the machine-readable rate-limit profile for Bitbucket Pipelines on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, minutes, and concurrent_steps.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include DevOps, CI/CD, Pipelines, Atlassian, and Bitbucket.

4 Limits Throttle: 429
DevOpsCI/CDPipelinesAtlassianBitbucketRate LimitingQuotasThrottling

Limits

Authenticated requests (per workspace / app installation) workspace_or_app
requests · 1h
60000
Unauthenticated requests ip
requests · 1h
1000
Pipelines step max duration step
minutes
120
Per-step build-time cap.
Concurrent steps workspace
concurrent_steps
tier-dependent
Free/Standard/Premium tiers have differing concurrency budgets.

Policies

Backoff Strategy
Honor Retry-After on 429; use exponential backoff with jitter.
Auth Recommendation
Use OAuth 2.0 / workspace access tokens / app passwords; avoid IP-based unauth calls.

Sources