Skip to main content
POST
/
builds
/
upload
/
complete
curl -X POST "https://nunu.ai/api/v1/builds/upload/complete" \
  -H "X-Api-Key: YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "build_id": "123e4567-e89b-12d3-a456-426614174000"
  }'

{
  "status": "success"
}
Permission Required: project:manage-build-storage
Complete a build upload. This finalizes the upload and makes the build available for use in test runs.

​
Request Body (Single-Part)

​
build_id
string
required
Build ID returned from initiate upload

​
Request Body (Multipart)

​
build_id
string
required
Build ID returned from initiate upload
​
upload_id
string
required
Upload ID returned from initiate upload
​
object_key
string
required
Object key returned from initiate upload
​
parts
Part[]
required
Array of uploaded parts with their ETags
For multipart uploads, parts must be in order by part_number. Missing or incorrectly ordered parts will cause completion to fail.

​
Response (Single-Part)

​
status
string
required
Always success

​
Response (Multipart)

​
build_id
string
required
The completed build ID
curl -X POST "https://nunu.ai/api/v1/builds/upload/complete" \
  -H "X-Api-Key: YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "build_id": "123e4567-e89b-12d3-a456-426614174000"
  }'

{
  "status": "success"
}

​
After Completion

Once the upload is complete, you can:

Use in Test Runs

Reference the build_id when starting runs

View in Dashboard

See the build under Builds in nunu.ai

Manage Storage

Old builds can be deleted via auto-delete policy

Authorizations

​
X-Api-Key
string
header
required

API key for authentication

Body

application/json
​
build_id
string
required

Build ID

​
upload_id
string

Upload ID (required for multipart)

​
object_key
string

Object key (required for multipart)

​
parts
object[]

Parts array (required for multipart)

Response

Upload completed successfully

​
status
string
​
build_id
string