Skip to main content
POST
Redeploy a project

Authorizations

x-brimble-key
string
header
required

API key created in the dashboard under Settings → API keys. Each key carries permission scopes; every endpoint lists the scope it needs.

Path Parameters

projectId
string
required
Pattern: ^[a-fA-F0-9]{24}$

Body

application/json
healthCheckPath
string
authEnabled
boolean
default:false
public
boolean
deleteVolume
boolean
http2
boolean
buildHealthCheck
boolean
preStartCommand
string
dockerfile
string
runtimeVersions
object
watchPaths
string[]
configurations
object
diskSize
integer
Required range: 10 <= x <= 150
volumeId
string
Pattern: ^[a-fA-F0-9]{24}$
mountPath
string
autoscalingGroup
string | null
serviceType
enum<string>
Available options:
web-service,
static,
mcp,
worker
cronEnabled
boolean
cronExpression
string
cronTimezone
string
cronCommand
string
sendReport
boolean
logId
string

Redeploy the commit from this earlier deployment.

Pattern: ^[a-fA-F0-9]{24}$
buildCacheEnabled
boolean | null
installCommand
string | null
buildCommand
string | null
startCommand
string | null
outputDirectory
string | null
rootDirectory
string | null
framework
string | null
repo
object | null
name
string

Project name. When present, the other settings in the body are saved to the project before redeploying.

specs
object | null
startOnly
boolean

Restart the current build without rebuilding.

Response

Operation success

message
string
required
Example:

"Operation success"

data
object
required
Last modified on October 10, 2026