Get Foundry Build

Returns a paginated list of Foundation OS builds registered in the Foundry system, with filters for architecture, Android version, device model, approval status, and more.

Use this endpoint to browse available Foundation builds for a specific device model — for example, to find all approved builds before initiating a Pipeline deployment or configuring auto-update.

About Get Foundry Builds

Foundry is Esper's build management backend for Foundation OS. Each Foundry build represents a compiled OS image tied to a specific device model, CPU architecture, and Foundation version. Builds go through a lifecycle — released, to_be_deprecated, or unavailable — and must be explicitly approved before they can be used for OTA deployment or auto-update. The Console surfaces these builds in the Esper Software Updates > Esper Foundation tab; this endpoint provides the same catalog programmatically.

Key Fields / Query Parameters

foundation_major_number — Filter by Foundation major version number (integer starting at 1)

build_arch — Filter by CPU architecture: arm, arm64, x86, or x86_64

android_major_version — Filter by Android major version (integer)

device_model_id — Filter builds for a specific device model (UUID)

approved — When true, returns only builds approved for OTA deployment

locked — Filter for builds currently locked to a device model; use with build_fingerprint_hash and device_model_id

build_fingerprint_hash — Hash of an existing build's fingerprint, used to identify a currently installed build

build_state — Lifecycle status: released, to_be_deprecated, or unavailable

Common Use Cases

Listing all approved Foundation builds for a device model before scheduling a Pipeline deployment or enabling auto-update

Auditing available builds by architecture and Android version across supported hardware

Identifying builds approaching deprecation (to_be_deprecated) to plan timely update campaigns

Best Practices

Always filter by approved=true when looking for builds eligible for deployment — unapproved builds cannot be used for OTA or auto-update

Filter by device_model_id to scope results to your target hardware, since builds are model-specific

Monitor build_state values and proactively migrate devices off to_be_deprecated builds before they become unavailable

Workflow

Call GET /v1/foundry/builds/ with device_model_id and approved=true to list eligible builds for your target hardware

Review build_arch, foundation_major_number, and android_major_version to identify the desired build

Use the returned build_id to approve the build (PUT /v1/foundry/builds/{build_id}/) or lock it for auto-update (PUT /v1/foundry/device-models/{device_model_id}/)