How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bitbucket Pipelines Branch restrictions API

Repository owners and administrators can set branch managementrules on a repository that control what can be pushed by whom.Through these rules, you can enforce a project or teamworkflow. For example, owners or administrators can:* Limit push powers* Prevent branch deletion* Prevent history re-writes (Git only)

Bitbucket Pipelines Branch restrictions API is one of 23 APIs that Bitbucket Pipelines publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Branch restrictions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 5 operations across 2 paths, and defines 9 schemas. It is described by OpenAPI 2.0, at version 2.0.

Requests are made against the base URL https://api.bitbucket.org/2.0.

5 operations 2 paths 9 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
2.0
Base URL
https://api.bitbucket.org/2.0
Authentication
basic, OAuth 2.0, API Key
Terms of Service
Resource Areas
1

Authentication & Security 3

Bitbucket Pipelines Branch restrictions API declares 3 security schemes for authenticating requests. It defines a basic scheme (basic). It supports OAuth 2.0 (oauth2) using the accessCode flow, exposing 26 scopes. An API key is passed in the header as Authorization (api_key).

  • basic — Basic HTTP Authentication as per [RFC-2617](https://tools.ietf.org/html/rfc2617) (Digest not supported). Note that Basic Auth is available only with username a…
  • oauth2 — OAuth 2 as per [RFC-6749](https://tools.ietf.org/html/rfc6749).
  • api_key — API Keys can be used as Basic HTTP Authentication credentials and provide a substitute for the account's actual username and password. API Keys are only availa…

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Branch restrictions 5

Repository owners and administrators can set branch management rules on a repository that control what can be pushed by whom. Through these rules, you can enforce a project or tea…

GET
/repositories/{workspace}/{repo_slug}/branch-restrictions
List branch restrictions
4 params → 200401403404
POST
/repositories/{workspace}/{repo_slug}/branch-restrictions
Create a branch restriction rule
3 params → 201401403404
DELETE
/repositories/{workspace}/{repo_slug}/branch-restrictions/{id}
Delete a branch restriction rule
3 params → 204401403404
GET
/repositories/{workspace}/{repo_slug}/branch-restrictions/{id}
Get a branch restriction rule
3 params → 200401403404
PUT
/repositories/{workspace}/{repo_slug}/branch-restrictions/{id}
Update a branch restriction rule
4 params → 200401403404

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are paginated_branchrestrictions (6 properties), error (2 properties), link (2 properties), account_links (1 property). Each schema is shown below with its type and property counts.

account
account_links
object
Links related to an Account.
1 property
paginated_branchrestrictions
object
A paginated list of branch restriction rules.
6 properties
branchrestriction
error
object
Base type for most resource objects. It defines the common type element that identifies an object's type. It also identifies the element as Swagger's discrimin…
2 properties 1 required
link
object
A link to a resource related to this object.
2 properties
group
workspace
object
object
Base type for most resource objects. It defines the common type element that identifies an object's type. It also identifies the element as Swagger's discrimin…
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bitbucket-pipelines-branch-restrictions-api-openapi.yml Raw ↑

Other APIs Bitbucket Pipelines publishes across the network.

Bitbucket Pipelines Addon API
Bitbucket Pipelines Branching model API
Bitbucket Pipelines Commit statuses API
Bitbucket Pipelines Commits API
Bitbucket Pipelines Deployments API
Bitbucket Pipelines Downloads API
Bitbucket Pipelines GPG API
Bitbucket Pipelines Issue tracker API
Bitbucket Pipelines Pipelines API
Bitbucket Pipelines Projects API
Bitbucket Pipelines properties API
Bitbucket Pipelines Pullrequests API
Where this information came from

This is an independent, third-party profile of Bitbucket Pipelines Branch restrictions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.