Skip to main content
POST
Create a build

Build Caching

Pipecat Cloud automatically caches successful builds based on three factors:
  1. Context hash - A hash of your uploaded context archive
  2. Region - The target deployment region
  3. Dockerfile path - The path to your Dockerfile
If a successful build already exists with the same combination, you’ll receive the cached build with cached: true. This makes repeated deployments much faster.

Build Flow

Example: Complete Build Flow

Build Statuses

Authorizations

Authorization
string
header
required

Authentication using a Pipecat Cloud API token.

Body

application/json
uploadId
string<uuid>
required

The upload ID returned from the upload-url endpoint.

Example:

"550e8400-e29b-41d4-a716-446655440000"

region
string
required

Target region for the build. Must match the region used when getting the upload URL.

Example:

"us-west"

dockerfilePath
string
default:Dockerfile

Path to the Dockerfile within the context archive.

Example:

"Dockerfile"

Response

Cached build found - no new build triggered

build
object
contextHash
string

Hash of the uploaded context. Used for build caching.

Example:

"a1b2c3d4e5f6a7b8"

cached
boolean

Whether this response uses a cached build (true) or triggered a new build (false).

Example:

false