Create a resource version

POST/v1/servers/{serverId}/versions

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
labelstringNo—
namestringNoBackwards-compatible alias for label
descriptionstringNoHuman-readable description.
snapshotobjectNo—
metadataobjectNoFree-form metadata object.
publishbooleanNo—

What the API returns

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

201Resource version createdapplication/json
FieldTypeRequiredDescription
versionobjectYes—
version.idstringYesUnique identifier.
version.versionintegerYes—
version.labelstringYes—
version.namestringYesHuman-readable name.
version.descriptionstringYesHuman-readable description.
version.statussaved | publishedYesCurrent lifecycle status.
version.snapshotobjectYes—
version.metadataobjectNoFree-form metadata object.
version.publishedAtstringNo—
version.createdAtstringYesISO 8601 timestamp.
version.updatedAtstringYesISO 8601 timestamp.
Create a resource version
Loading...
Response 201
Loading...
See the ACP quickstart and SDK flow