Skip to main content
GET
/
builds
/
{buildId}
/
logs
Get build logs
curl --request GET \
  --url https://api.pipecat.daily.co/v1/builds/{buildId}/logs \
  --header 'Authorization: Bearer <token>'
{
  "logs": [
    "[Container] 2026/03/04 10:00:00 Entering phase: INSTALL",
    "[Container] 2026/03/04 10:00:01 Running command pip install -r requirements.txt",
    "[Container] 2026/03/04 10:00:05 Successfully installed pipecat-ai-0.1.0"
  ],
  "nextToken": "eyJuZXh0VG9rZW4iOiAiYWJjMTIzIn0="
}

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.

​
Streaming Logs During Build

You can poll this endpoint during a build to stream logs in real-time. The endpoint returns the latest logs each time you call it: 
BUILD_ID="123e4567-e89b-12d3-a456-426614174000"

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

  echo "$RESPONSE" | jq -r '.logs[]'

  # Check if build is still in progress
  BUILD_STATUS=$(curl -s "https://api.pipecat.daily.co/v1/builds/$BUILD_ID" \
    -H "Authorization: Bearer $PIPECAT_API_KEY" | jq -r '.build.status')

  if [[ "$BUILD_STATUS" == "success" || "$BUILD_STATUS" == "failed" || "$BUILD_STATUS" == "timeout" ]]; then
    echo "Build finished with status: $BUILD_STATUS"
    break
  fi

  sleep 5
done

​
Pagination

Use the limit query parameter to control how many log lines are returned:
ParameterDefaultMinMaxDescription
limit500110,000Number of log events to return
Logs may be empty if the build was just created and hasn’t started executing yet. Continue polling until logs appear or the build completes.

​
Debugging Failed Builds

When a build fails, use this endpoint to diagnose the issue: 
BUILD_ID="123e4567-e89b-12d3-a456-426614174000"

# Get the full build logs
curl -s "https://api.pipecat.daily.co/v1/builds/$BUILD_ID/logs?limit=10000" \
  -H "Authorization: Bearer $PIPECAT_API_KEY" | jq -r '.logs[]'
Common issues visible in build logs include:
  • Missing dependencies in requirements.txt
  • Dockerfile syntax errors
  • Failed pip install commands
  • Missing files referenced in COPY instructions

Authorizations

​
Authorization
string
header
required

Authentication using a Pipecat Cloud API token.

Path Parameters

​
buildId
string<uuid>
required

Unique identifier of the build.

Query Parameters

​
limit
integer
default:500

Maximum number of log events to return.

Required range: 1 <= x <= 10000

Response

Build logs retrieved successfully

​
logs
string[]
required

Array of log lines from the build process. May be empty if the build hasn't started generating logs yet.

Example:
[
  "[Container] 2026/03/04 10:00:00 Entering phase: INSTALL",
  "[Container] 2026/03/04 10:00:01 Running command pip install -r requirements.txt",
  "[Container] 2026/03/04 10:00:05 Successfully installed pipecat-ai-0.1.0"
]
​
nextToken
string

Pagination token for retrieving additional logs. Present when more logs are available.

Example:

"eyJuZXh0VG9rZW4iOiAiYWJjMTIzIn0="