Publish a resource version
POST
/v1/servers/{serverId}/versions/{versionId}/publishHow 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
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| serverId | path | string | Yes | Resource ID |
| versionId | path | string | Yes | Immutable saved resource version ID |
Query parameters
None.
Body schema
Content type: application/json · Optional
| Field | Type | Required | Description |
|---|---|---|---|
| label | string | No | — |
| name | string | No | Backwards-compatible alias for label |
| description | string | No | Human-readable description. |
| snapshot | object | No | — |
| metadata | object | No | Free-form metadata object. |
| publish | boolean | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Resource version published
None.