# Build Details

> Retrieve detailed information about your Applivery Builds using the Integrations and Workspace APIs, including endpoints and authentication.

Source: https://docs.applivery.com/en/app-distribution/api/builds/build-details/  •  Last updated: 2026-04-28

**Key topics:** Applivery API, Build Details, Integrations API, Workspace API, API Authentication, Applivery, App API Token, Service Account

---

**TL;DR:** Retrieve detailed information about Applivery builds using either the per-app Integrations API or the workspace-level Workspace API, each requiring different authentication methods.

Returns the full details of a single build, identified by its `buildId`. This is the primary endpoint for inspecting the processing status, metadata, and platform-specific information of a specific Build — and the recommended endpoint for polling after an upload until the Build reaches a terminal state (`processed` or `error`).

Applivery provides two separate APIs for retrieving build details, each requiring a different authentication credential.

* * *

## Choosing the Right API

|  | Integrations API | Workspace API |
| --- | --- | --- |
| **Designed for** | Per-app integrations, CI/CD pipelines, post-upload status polling | Workspace-level automation across multiple Apps |
| **Authentication** | App API Token (per-app) | Service Account token (Workspace-level) |
| **App context** | Implicit — token is already scoped to an App | Explicit — `organizationId` and `applicationId` required in the path |
| **Typical users** | CI scripts checking if a Build has finished processing | Platform engineers inspecting Builds across multiple Apps |

:::warning
Access to the different APIs might not be available in your current plan. Please check availability on our [pricing page](https://www.applivery.com/app-distribution-pricing/).
:::

* * *

## Integrations API

Use this endpoint when retrieving build details within the scope of a single app. Authentication uses an **App API Token**, scoped to the specific App.

To create an App API Token, see [Apps API Authentication](https://docs.applivery.com/en/app-distribution/api/app-api-token/).

### Endpoint

```
GET https://api.applivery.io/v1/integrations/builds/{buildId}
```

### Authentication

```
Authorization: Bearer <your_app_token>
```

### Path Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `buildId` | String | Yes | The unique identifier of the Build to retrieve. E.g. `552ae3cfcb5abfc58d733b81`. The `buildId` is returned in the response of POST – Upload a Build and GET – List of Builds. |

### Example Request

```bash
curl 'https://api.applivery.io/v1/integrations/builds/552ae3cfcb5abfc58d733b81' \
  -X GET \
  -H 'Authorization: Bearer YOUR_APP_TOKEN'
```

### Responses

**✓ 200 OK**

```json
{
  "status": true,
  "data": {
    "id": "string",
    "status": "processed",
    "tags": ["string"],
    "versionName": "string",
    "application": "string",
    "applicationInfo": {
      "id": "string",
      "name": "string",
      "slug": "string",
      "picture": "string"
    },
    "changelog": "string",
    "info": {
      "icon": "string",
      "android": {
        "targetSdkVersion": "string",
        "minSDKVersion": "string",
        "packageName": "string",
        "platformBuildVersionName": "string",
        "platformBuildVersionCode": "string",
        "versionName": "string",
        "versionCode": "string",
        "icon": "string"
      },
      "ios": {
        "plist": {
          "CFBundleDisplayName": "string",
          "CFBundleSupportedPlatforms": ["string"],
          "MinimumOSVersion": "string",
          "CFBundleIdentifier": "string",
          "CFBundleShortVersionString": "string",
          "CFBundleVersion": "string",
          "CFBundleName": "string",
          "CFBundleIcons": ["string"],
          "UIDeviceFamily": ["string"]
        },
        "mobileprovision": {
          "ExpirationDate": "2019-08-24T14:15:22Z",
          "TeamIdentifier": "string",
          "ProvisionsAllDevices": true,
          "TeamName": "string",
          "ProvisionedDevices": "string",
          "signingType": "ad-hoc"
        }
      },
      "pkg": {
        "CFBundleDisplayName": "string",
        "CFBundleIdentifier": "string",
        "CFBundleShortVersionString": "string",
        "CFBundleVersion": "string",
        "CFBundleName": "string"
      }
    },
    "size": 0,
    "processTime": 0,
    "queuedTime": 0,
    "versionCode": "string",
    "error": "string",
    "errorCode": "string",
    "os": "ios",
    "deployer": {
      "name": "string",
      "info": {
        "commitMessage": "string",
        "commit": "string",
        "branch": "string",
        "triggerTimestamp": "string",
        "buildUrl": "string",
        "ciUrl": "string",
        "repositoryUrl": "string",
        "buildNumber": "string",
        "tag": "string"
      }
    },
    "uploadedBy": {
      "id": "string",
      "email": "user@example.com",
      "firstName": "string",
      "lastName": "string",
      "picture": "string"
    },
    "originalExtension": "string",
    "storageProvider": {
      "id": "string",
      "name": "string",
      "region": "string"
    },
    "hasEmmJson": true,
    "updatedAt": "2019-08-24T14:15:22Z",
    "createdAt": "2019-08-24T14:15:22Z"
  }
}
```

**✗ 400 Bad Request**

Build not yet processed. This error is returned when the Build exists but has not yet completed processing. Retry after a short delay.

```json
{
  "status": false,
  "error": {
    "code": 5014,
    "message": "Build Not Processed"
  }
}
```

**✗ 401 Unauthorized**

```json
{
  "status": false,
  "error": {
    "code": 3002,
    "message": "Token Expired"
  }
}
```

**✗ 404 Not Found**

```json
{
  "status": false,
  "error": {
    "code": 3001,
    "message": "Entity not found"
  }
}
```

### Key response fields

| Field | Description |
| --- | --- |
| `status` | Processing status of the Build: `pending`, `in_progress`, `processed`, or `error`. |
| `error` | Human-readable error message, populated only when `status` is `error`. |
| `errorCode` | Machine-readable error code for programmatic handling. See Build Processing Codes. |
| `info.android` | Extracted Android metadata: package name, version name, version code, SDK targets, and icon. Only present for Android Builds. |
| `info.ios.plist` | Extracted iOS `Info.plist` metadata: bundle identifier, version, display name, supported platforms, and device families. Only present for iOS Builds. |
| `info.ios.mobileprovision` | iOS provisioning profile details: team, expiration date, signing type, and provisioned Devices. Only present for iOS Builds. |
| `info.pkg` | Extracted macOS package metadata. Only present for macOS Builds. |
| `deployer` | CI/CD metadata attached at upload time: branch, commit, build number, and platform URLs. |
| `size` | Build file size in bytes. |
| `processTime` | Time taken to process the Build, in milliseconds. |

:::tip
After uploading a Build, call this endpoint periodically with the `buildId` returned from the upload response until `status` is `processed` or `error`. A `status` of `pending` or `in_progress` means processing is still ongoing. If the status is `error`, check the `errorCode` field and refer to [Build Processing Codes](https://docs.applivery.com/en/app-distribution/builds/processing-error-codes/) for resolution steps.
:::

* * *

## Workspace API

Use this endpoint when retrieving build details at the Workspace level — for example, in automation that operates across multiple Apps using a single credential.

Authentication uses a **Service Account** token, which is Workspace-scoped and not tied to any individual app. The App and build context are both provided via path parameters.

To create a Service Account, see [Service Accounts](https://docs.applivery.com/en/platform/api/service-accounts/).

### Endpoint

```
GET https://api.applivery.io/v1/organizations/{organizationId}/apps/{applicationId}/builds/{buildId}
```

### Path Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `organizationId` | String | Yes | The unique identifier of your Applivery organization. |
| `applicationId` | String | Yes | The unique identifier of the App the Build belongs to. |
| `buildId` | String | Yes | The unique identifier of the Build to retrieve. |

### Authentication

```
Authorization: Bearer <your_service_account_token>
```

### Example Request

```bash
curl 'https://api.applivery.io/v1/organizations/ORG_ID/apps/APP_ID/builds/552ae3cfcb5abfc58d733b81' \
  -X GET \
  -H 'Authorization: Bearer YOUR_SERVICE_ACCOUNT_TOKEN'
```

The response schema is identical to the Integrations API.