Skip to main content
POST
Rebase Branch

Authentication and permissions

Token requirements: User-based token (OAuth). Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Workspace keys must allow every workspace checked by the request. OAuth access depends on the user’s roles and resource access.
  • User: branch rebase: Requires branch-copy permission on the actual parent workspace and staging permission on the branch. Clean rebases also require permission to apply configuration on the branch and must pass its approval, CI, and freshness checks. Conflicts return a review for manual application. API keys are not supported.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

branch_team_id
string
required

Response

200 - application/json

Success

data
data · object