Skip to main content
GET
/
builds
/
{buildId}
Get build status
curl --request GET \
  --url https://api.pipecat.daily.co/v1/builds/{buildId} \
  --header 'Authorization: Bearer <token>'
{
  "build": {
    "id": "123e4567-e89b-12d3-a456-426614174000",
    "organizationId": "org_abc123",
    "status": "success",
    "region": "us-west",
    "contextHash": "a1b2c3d4e5f6a7b8",
    "dockerfilePath": "Dockerfile",
    "imageUri": "123456789.dkr.ecr.us-west-2.amazonaws.com/pipecat-cloud/org_abc123:a1b2c3d4e5f6a7b8",
    "logsUrl": "https://console.aws.amazon.com/codebuild/...",
    "errorMessage": "Docker build failed: COPY failed - file not found: requirements.txt",
    "contextSizeBytes": 10485760,
    "imageSizeBytes": 524288000,
    "buildDurationSeconds": 120,
    "startedAt": "2026-02-20T12:00:00.000Z",
    "completedAt": "2026-02-20T12:02:00.000Z",
    "createdAt": "2026-02-20T12:00:00.000Z",
    "updatedAt": "2026-02-20T12:02:00.000Z"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.pipecat.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Status Reconciliation

When you poll a build that’s in progress (pending or building), Pipecat Cloud automatically reconciles the status with the underlying build system. This means you always get the latest status without any delay.

​
Polling for Completion

After creating a build, poll this endpoint until the build completes: 
BUILD_ID="123e4567-e89b-12d3-a456-426614174000"

while true; do
  RESPONSE=$(curl -s "https://api.pipecat.daily.co/v1/builds/$BUILD_ID" \
    -H "Authorization: Bearer $PIPECAT_API_KEY")

  STATUS=$(echo $RESPONSE | jq -r '.build.status')

  case $STATUS in
    "success")
      IMAGE_URI=$(echo $RESPONSE | jq -r '.build.imageUri')
      echo "Build complete! Image: $IMAGE_URI"
      break
      ;;
    "failed"|"timeout")
      ERROR=$(echo $RESPONSE | jq -r '.build.errorMessage')
      echo "Build failed: $ERROR"
      exit 1
      ;;
    *)
      echo "Status: $STATUS - waiting..."
      sleep 10
      ;;
  esac
done
Once your build succeeds, use the Pipecat CLI to deploy your agent. The CLI will automatically use the built image.

Authorizations

​
Authorization
string
header
required

Authentication using a Pipecat Cloud API token.

Path Parameters

​
buildId
string<uuid>
required

Unique identifier of the build.

Response

Build details

​
build
object