Roll resource traffic back to a previous deployment revision

POST/v1/servers/{serverId}/rollback

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
serverIdpathstringYesResource ID
Query parameters
None.

Body schema

Content type: application/json · Optional

FieldTypeRequiredDescription
deploymentIdstringNoDeployment history id to restore. If omitted, the latest previous successful revision is used.
revisionstringNoCloud Run revision to restore.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Resource rolled backapplication/json
FieldTypeRequiredDescription
serverobjectNo—
server.idstringNoUnique identifier.
server.userIdstringNoUser ID.
server.organizationIdstringNo—
server.createdByUserIdstringNo—
server.projectIdstringNoProject ID.
server.namestringNoHuman-readable name.
server.descriptionstringNoHuman-readable description.
server.kindwebsite | web_app | api | function | auth | agent_runtime | secrets | paymentsNo—
server.sourceTypestringNo—
server.sourceEnvironmentIdstringNo—
server.sourcePathstringNoWorkspace-relative file path.
server.regionstringNo—
server.runtimestringNo—
server.authModepublic | privateNo—
server.serviceUrlstringNo—
server.customDomainstringNo—
server.cloudRunServiceNamestringNo—
server.imageUrlstringNo—
server.statusdraft | deploying | deployed | failed | inactiveNoCurrent lifecycle status.
server.lastDeployedAtstringNo—
server.metadataobjectNoFree-form metadata object.
server.createdAtstringNoISO 8601 timestamp.
server.updatedAtstringNoISO 8601 timestamp.
deploymentobjectNo—
deployment.idstringNoUnique identifier.
deployment.atstringNo—
deployment.outcomesuccess | failed | rollbackNo—
deployment.typestringNo—
deployment.serviceNamestringNo—
deployment.regionstringNo—
deployment.revisionstringNo—
deployment.serviceUrlstringNo—
deployment.imageUrlstringNo—
deployment.runtimestringNo—
deployment.authModestringNo—
deployment.sourceEnvironmentIdstringNo—
deployment.sourcePathstringNoWorkspace-relative file path.
deployment.connectionsobjectNo—
deployment.errorstringNo—
deployment.rolledBackToDeploymentIdstringNo—
deployment.versionBindingobjectNo—
deployment.versionBinding.schemaVersioncomputer_agents_server_deployment_version_binding_v1Yes—
deployment.versionBinding.versionIdstringYes—
deployment.versionBinding.versionNumberintegerYes—
deployment.versionBinding.snapshotFingerprintstringYes—
activeDeploymentobjectNo—
activeDeployment.idstringNoUnique identifier.
activeDeployment.atstringNo—
activeDeployment.outcomesuccess | failed | rollbackNo—
activeDeployment.typestringNo—
activeDeployment.serviceNamestringNo—
activeDeployment.regionstringNo—
activeDeployment.revisionstringNo—
activeDeployment.serviceUrlstringNo—
activeDeployment.imageUrlstringNo—
activeDeployment.runtimestringNo—
activeDeployment.authModestringNo—
activeDeployment.sourceEnvironmentIdstringNo—
activeDeployment.sourcePathstringNoWorkspace-relative file path.
activeDeployment.connectionsobjectNo—
activeDeployment.errorstringNo—
activeDeployment.rolledBackToDeploymentIdstringNo—
activeDeployment.versionBindingobjectNo—
activeDeployment.versionBinding.schemaVersioncomputer_agents_server_deployment_version_binding_v1Yes—
activeDeployment.versionBinding.versionIdstringYes—
activeDeployment.versionBinding.versionNumberintegerYes—
activeDeployment.versionBinding.snapshotFingerprintstringYes—
Roll resource traffic back to a previous deployment revision
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow