Upload a build

# 1. get a signed upload URL
RESP=$(curl -sS -X POST \
  -H "Authorization: Bearer $CLICKPROOF_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"sizeBytes\": $(wc -c < app.apk)}" \
  https://clickproof.app/api/v1/projects/YOUR_PROJECT_ID/build/upload-url)
BUILD_ID=$(echo "$RESP" | jq -r .buildId)
UPLOAD_URL=$(echo "$RESP" | jq -r .uploadUrl)

# 2. upload the build straight to storage
curl -sS --fail -X PUT --upload-file app.apk "$UPLOAD_URL"

# 3. confirm
curl -sS -X POST \
  -H "Authorization: Bearer $CLICKPROOF_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"buildId\": \"$BUILD_ID\"}" \
  https://clickproof.app/api/v1/projects/YOUR_PROJECT_ID/build/confirm

{
  "ok": true,
  "projectId": "7f3a9c21-4e8b-45d2-9a1c-2b6e0f8d1a44",
  "buildId": "asset_9c1d4e5f6a7b"
}

# 1. get a signed upload URL
RESP=$(curl -sS -X POST \
  -H "Authorization: Bearer $CLICKPROOF_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"sizeBytes\": $(wc -c < app.apk)}" \
  https://clickproof.app/api/v1/projects/YOUR_PROJECT_ID/build/upload-url)
BUILD_ID=$(echo "$RESP" | jq -r .buildId)
UPLOAD_URL=$(echo "$RESP" | jq -r .uploadUrl)

# 2. upload the build straight to storage
curl -sS --fail -X PUT --upload-file app.apk "$UPLOAD_URL"

# 3. confirm
curl -sS -X POST \
  -H "Authorization: Bearer $CLICKPROOF_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"buildId\": \"$BUILD_ID\"}" \
  https://clickproof.app/api/v1/projects/YOUR_PROJECT_ID/build/confirm

{
  "ok": true,
  "projectId": "7f3a9c21-4e8b-45d2-9a1c-2b6e0f8d1a44",
  "buildId": "asset_9c1d4e5f6a7b"
}

Uploading a build is a three-step handshake: request a signed upload URL, PUT the file straight to storage, then confirm. The build bytes never pass through the clickproof API itself, so there is no request-size cap in the way - builds up to 600 MB work.

Request an upload URL

POST /api/v1/projects//build/upload-url

string

required

The project id, in the URL path.

string

required

Bearer <your API key>.

number

The build’s size in bytes. Optional, but sending it turns an over-limit upload into an instant 413 instead of a wasted transfer.

string

Id of the build asset. Pass it to confirm.

string

Signed storage URL. Valid for a single build upload; do not log it.

PUT the build to the upload URL

Send the raw file bytes with a plain PUT - no auth header, the URL is self-authorizing.

Confirm

POST /api/v1/projects//build/confirm

string

required

The buildId from step 1.

The confirmed build replaces the project’s current build. The size is verified against what actually landed in storage.

boolean

true on success.

string

The project the build was attached to.

string

Id of the stored build asset.

# 1. get a signed upload URL
RESP=$(curl -sS -X POST \
  -H "Authorization: Bearer $CLICKPROOF_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"sizeBytes\": $(wc -c < app.apk)}" \
  https://clickproof.app/api/v1/projects/YOUR_PROJECT_ID/build/upload-url)
BUILD_ID=$(echo "$RESP" | jq -r .buildId)
UPLOAD_URL=$(echo "$RESP" | jq -r .uploadUrl)

# 2. upload the build straight to storage
curl -sS --fail -X PUT --upload-file app.apk "$UPLOAD_URL"

# 3. confirm
curl -sS -X POST \
  -H "Authorization: Bearer $CLICKPROOF_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"buildId\": \"$BUILD_ID\"}" \
  https://clickproof.app/api/v1/projects/YOUR_PROJECT_ID/build/confirm

{
  "ok": true,
  "projectId": "7f3a9c21-4e8b-45d2-9a1c-2b6e0f8d1a44",
  "buildId": "asset_9c1d4e5f6a7b"
}

Errors

Status	Body	When
`400`	`buildId is required`	Confirm called without a `buildId`.
`400`	`that buildId does not belong to this project`	The id is not this project’s build asset.
`400`	`no uploaded build found`	Confirm called before the `PUT` finished (or it failed).
`413`	`build exceeds the 600MB limit`	Build too large (declared or actual).
`404`	`project not found`	No such project for your team.
`502`	upstream message	The build store rejected the request.

Legacy single-request upload

POST /api/v1/projects//build

The older endpoint still accepts the raw build bytes as the request body (Content-Type: application/octet-stream) and responds with the same { ok, projectId, buildId }. It only works for builds under ~100 MB - the platform edge rejects larger request bodies with a 413 before they reach the API. New integrations should use the upload-url / confirm pair above.

Overview

Endpoints

Errors

Legacy single-request upload

​Errors

​Legacy single-request upload

Errors

Legacy single-request upload