Skip to main content
GET
Get a serverless endpoint build

Authorizations

Authorization
string
header
required

Runpod API key authentication. Generate an API key in the Runpod console and send it in the Authorization header as Bearer <api_key>. Keys are scoped to the permissions granted when created; requests may return 403 when a valid key lacks access to the requested resource or action.

Path Parameters

id
string
required

Serverless endpoint identifier

buildId
string
required

GitHub build identifier (from GET /v2/serverless/{id}/builds or a release's buildId)

Response

OK

id
string
required
Example:

"build_abc123"

status
enum<string>
required

GitHub build lifecycle state. COMPLETED, FAILED, CANCELLED, and TEST_FAILED are terminal; PENDING, BUILDING, UPLOADING, and TESTING are live.

Available options:
PENDING,
BUILDING,
UPLOADING,
TESTING,
COMPLETED,
FAILED,
CANCELLED,
TEST_FAILED
commitHash
string | null

Short hash of the commit that triggered the build.

Example:

"abc1234"

commitMessage
string | null
Example:

"bump model"

branch
string | null

Git branch the commit was pushed to.

Example:

"main"

commitDate
string<date-time> | null

When the triggering commit was authored.

Example:

"2026-06-01T12:00:00Z"

imageName
string | null

Fully qualified image the build produced (or will produce).

Example:

"registry.runpod.net/repo:abc1234"

startedAt
string<date-time> | null

When the build started. Null while the build is still pending.

Example:

"2026-06-01T12:00:05Z"

completedAt
string<date-time> | null

When the build reached a terminal state. Null while the build is live.

Example:

"2026-06-01T12:04:31Z"

error
string | null

Failure detail for FAILED / TEST_FAILED builds; null otherwise.

Last modified on September 3, 2026