Interlaken
API referenceAgents and workflowsWorkspaces

Read one deployment's BUILD LOG by uuid (from the deployments list). Use this to find out why a specific build failed before changing any code.

GET
/api/v1/workspaces/{id}/cicd/deployments/{deployment}/log

Requires the workspaces:read permission.

Authorization

AuthorizationBearer <token>

An access token from this zone's POST /oauth/token, or a session token from POST /api/v1/auth/login. Send it as Authorization: Bearer <token>.

In: header

Path Parameters

id*string
deployment*string

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/api/v1/workspaces/string/cicd/deployments/string/log"
{  "app": "string",  "logs": "string",  "status": "string",  "uuid": "string"}

List the workspace app's deployment history (status + commit per deploy). A store lists BOTH apps — check the app field, since backend and storefront fail independently. GET

Previous Page

Read the BUILD LOG of the workspace's most recent deployment. This is the first thing to read when a deploy failed — it carries the compiler/installer output that says why. For an older deploy, take its uuid from the deployments list and use the /log variant. GET

Next Page