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, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring requests, minutes, and concurrent_steps.
Limit state is signalled in the X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and Retry-After response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
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.
X-RateLimit-LimitX-RateLimit-RemainingX-RateLimit-ResetRetry-After
generated, dated 2026-05-08.
Limits
Policies
Sources
- https://support.atlassian.com/bitbucket-cloud/docs/api-request-limits/
- https://support.atlassian.com/bitbucket-cloud/docs/build-minutes/
- https://support.atlassian.com/bitbucket-cloud/docs/pipelines-configuration-reference/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.