Cloud endpoint

Create Machine Configuration Version

POST/machine-configurations/{configurationId}/versions/

Path parameters

configurationId

Identifier used by the registered route.

Example request

application/json

{
  "version": 1,
  "playbookYaml": "- hosts: all\n  tasks:\n    - ansible.builtin.debug:\n        msg: ready\n"
}

cURL template

curl --fail-with-body \
  -H "Authorization: Bearer ${AKOFLOW_API_TOKEN}" \
  -H "Content-Type: application/json" \
  --data-binary @request.json \
  -X POST \
  "${AKOFLOW_API_URL}/machine-configurations/{configurationId}/versions/"

Supply a valid request.json before running this command.

Replace the path identifiers with IDs from your instance.

201 Createdapplication/json

Field shape inferred from Go types; inspect the returned JSON for actual values and optional fields.

{
  "id": "string",
  "name": "string",
  "description": "string",
  "ownership": "string",
  "enabled": true,
  "versions": [
    {
      "id": "string",
      "machineConfigurationId": "string",
      "version": 0,
      "status": "string",
      "playbookYaml": "string",
      "contentSha256": "string",
      "compatibility": {},
      "variablesSchema": {},
      "validationChecks": [],
      "createdAt": "2026-01-01T00:00:00Z"
    }
  ],
  "createdAt": "2026-01-01T00:00:00Z",
  "updatedAt": "2026-01-01T00:00:00Z"
}

Handler-checked behavior

Create the configuration first, then use its returned ID as configurationId (the preceding example uses example-machine-setup). The path ID overrides any body machineConfigurationId. Send a positive version and valid playbookYaml; id is optional and status defaults to draft. The response is the stored configuration with its versions, not just the new version.

Related guide

See the Cloud guide for related tasks and context.