computer agents developers

Deploy resource

POST/v1/servers/{serverId}/deploy

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

This endpoint does not require a request body.

None.

What the API returns

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

200Resource deployedapplication/json
FieldTypeRequiredDescription
serverobjectNo—
server.idstringNoUnique identifier.
server.userIdstringNoUser ID.
server.projectIdstringNoProject ID.
server.namestringNoHuman-readable name.
server.descriptionstringNoHuman-readable description.
server.kindweb_app | function | auth | agent_runtimeNo—
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.
serviceUrlstringNo—
invocationUrlstringNo—
revisionstringNo—
deploymentTypestringNo—
Deploy resource
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow