Artifacts endpoint

Create Artifact Build

POST/artifact-builds/

Request body

application/json

See the request guidance below for a valid body.

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}/artifact-builds/"

Supply a valid request.json before running this command.

200 OKapplication/json

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

{
  "id": "string",
  "artifactVersionId": "string",
  "sourceType": "string",
  "contextDigest": "string",
  "recipePath": "string",
  "recipeDigest": "string",
  "targetFormat": "string",
  "targetOs": "string",
  "targetArchitecture": "string",
  "buildArguments": "string",
  "cacheKey": "string"
}

201 Created

Handler-checked behavior

Upload the build context first and use its returned digest as contextDigest; artifactVersionId must identify a saved artifact version. Required fields are id, artifactVersionId, contextDigest, recipeDigest, and cacheKey. An existing cache key returns that build with 200 OK; a new specification returns 201 Created. Creating a specification does not start a build run. See Build an executable for the simpler Docker-image path.

Related guide

See the Artifacts guide for related tasks and context.