---
title: Uploading binary files to Ivanti incapptic Connect through an API
slug: incappticconnect/user_guide/uploading-binary-files-to-ivanti-incapptic-connect-through-an-api
docTags: 
createdAt: 2026-09-10T14:29:45.689Z
---

You can upload app binary files (\*.apk, \*.ipa) without a web interface through the Ivanti incapptic Connect command line. This is done by using the cURL utility to send the file to Ivanti incapptic Connect, along with a verification token, and information about the app being uploaded.

:::CodeblockTabs
Command

```curl
curl -X POST
https://<<domain_name>>/apps/upload-artifact \
-H 'x-connect-token: <<token>>' \
-F 'artifact-4=@/Users/developer/apps/built_app_v13.ipa'
```
:::



The cURL request would be similar to this example:

:::CodeblockTabs
Command

```curl
curl -X POST
https://connect.incapptic.net/apps/upload-artifact \
-H 'x-connect-token: 1:T7NH978v9qwyVH64HgqQrGqEX6NvH3dvm9f6vsUarJVs3NXBcf5AGDNmtZ4rvxt2' \
-F 'artifact-4=@/Users/developer/apps/built_app_v13.ipa'
```
:::

## Creating a cURL request

**Prerequisites**

Obtain a valid API token. See [Generating an API token](docId\:CHdSejLQ4-sgNR-AaZXYp).

**Procedure&#xA0;**

1. From the **Apps&#x20;**&#x70;age, click an app to open it.
2. Click the **API&#x20;**&#x74;ab.&#x20;
   The API section opens.

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/IjpmEvUztcaIdxzNHTCRg_uploading-binary-files-to.png" alt="A screenshot of a cell phone&#xA;&#xA;Description automatically generated" position="flex-start" size="58" width="576" height="203" initialPath="../Resources/Images/ic_user_guide_v3_pt2/Uploading binary files to.png" githubPath="incapptic_Connect_ug/Resources/Images/ic_user_guide_v3_pt2/Uploading binary files to.png" darkWidth="576" darkHeight="203" showCaption="false" indent="1"}

3. Click the **API upload** switch to enable it.&#x20;
   The Upload URL and the Application ID fields become visible.
4. Copy the fields and paste them into your cURL snippet.
5. Enter the API token value you obtained in [Generating an API token](docId\:CHdSejLQ4-sgNR-AaZXYp).

:::hint{type="info" indent="1"}
The number preceding the token is a reference to the user’s ID and must be included as part of the token.
:::

**Limitations**:

- The API can only be used to upload a version if a version of the App with all the associated metadata (copyright, content rating etc.) has previously been uploaded. In other words, the API can only be used to upload a binary file. A new version of the app will be created, using the metadata from the previous version.
- The binary file must be valid, and it must be a different version to the version that currently exists.

:::hint{type="info"}
The reference to artifact in the API arises from the fact that the API was originally developed to work together with [Jenkins](https://jenkins.io/), a continuous integration platform. Jenkins has the concept of an "artifact" which essentially refers to the file, or the binary.
:::

