Skip to main content
PATCH
Patch Project

Authorizations

Authorization
string
header
required

Get access to data with your API token. Example header:

Authorization: Bearer 2991e2fb4b540fe75b8f90677b0b892b6314e4961cb001fe6eb452eee248a628

The token can be provisioned from the Tokens section in your Settings, and requires explicitly enabling Web API access.

Path Parameters

deploymentId
string<int64>
required

The unique numerical identifier for the deployment.

Example:

123

idOrName
string<int64 | name-slug>
required

A unique identifier for the project to modify. For example, 456 for uint64 ID or "my-org/my-repo" for name-slug.

Example:

456

Body

application/json
deploymentId
string<int64>

The unique numerical identifier for the deployment.

Example:

123

idOrName
string<int64 | name-slug>

A unique identifier for the project to modify. For example, 456 for uint64 ID or "my-org/my-repo" for name-slug.

Example:

456

name
string

The new name for the project. If not provided, the project name will not be changed.

Example:

"my-new-project"

managedScans
Managed Scan Settings · object
tagsChanges
Tags Changes · object[]

The change(s) to apply to the project's tags.

primaryBranch
string

The new primary branch for the project. If not provided, the project's primary branch will not be changed.

If you set primary_branch to "None", the project's primary branch will be set to the project's default branch, if known.

Note: the project's "default branch" is detected from your source code manager. The "primary branch" will override the default branch.

Example:

"refs/heads/deploy"

aiScans
AI Scan Settings · object

Response

200 - application/json

OK

repo
object