Automate Single Tasks using the Appdome-DEV REST API

This Knowledge Base article outlines how you can use the Appdome REST API to automate building your mobile app, in order to automate deployment and continuous integration and continuous delivery (CI/CD) workflows.

We hope you find this knowledge base useful and enjoy using Appdome!

Appdome-DEV Single Task API

In addition to the Build-to-Publish API, Appdome-DEV also offers a step by step access to the steps of building an app on Appdome, from Upload to Building, Adding Context and Singing the app.

This article details the technical specifications of these API requests.

Prerequisites for Using the Appdome Build REST API

In order to use Appdome’s REST API, you’ll need:

• An Ideal Appdome account.
• Appdome-DEV access
• Your API Token (See how to get your API Token)
• If you’re Building on an App Team – Team API Key
• A Fusion Set API KEY (See how to get Fusion Set API Key)
• If you’re Building on an App Team – The Fusion Set API KEY on the App Team

The Task requests generally are sequential so each task uses an identifier from a previous task to complete. For instance, the Upload task returns an Application ID, that is then sent to the Build Task.

Uploading Apps using the Appdome-DEV REST API

curl -X POST -H "Authorization:dkG90pp9LPsXUC_pPWO0qA" https://fusion.appdome.com/api/v1/upload -F "file=@/path/to/file.apk"

curl -X POST -H "Authorization:dkG90pp9LPsXUC_pPWO0qA" "https://fusion.appdome.com/api/v1/upload?team_id=33392-23232-1451-987" -F "file=@/path/to/file.apk"

{
    "app": {
        "id": Application ID,
        "account_id": Application Account ID,
        "user_id": Application User ID,
        "creation_time": Unix Time,
        "pack_name": App File Name,
        "pack_size": Size in Bytes,
        "pack_type": apk/ipa,
        "pack_bundle_identifier": App Bundle ID,
        "pack_bundle_version": App Bundle Version,
        "pack_bundle_display_name": App Display Name,
        "pack_bundle_build_number": App Build Number,
        "pack_app_store_description": App Store Description If exist,
        "status": active/error
    } 
}

Building Apps using the Appdome-DEV REST API

After uploading your app and getting the Application ID, you can now build it using an existing Fusion Set.

-F app_id=<Application ID> //(from the Upload task response)
-F fusion_set_id=<Your_Fusion_set_API_Key>
-F action=fuse
-F 'overrides={<overrides, or empty JSON>}' //(see details below)
-F plugin_good_private_certs_content=@<path/to/single/file> //(optional)

curl -X POST -H "Authorization: dkG90pp9LPsXUC_pPWO0qA" -F app_id=pl5ZsekOBadRbbZHDGMYUw -F fusion_set_id=vpRwZCDTBW2IfmOFpvHpxA -F action=fuse -F 'overrides={"user_agent":true, "user_agent_value":"Mozilla 5.5"}' -H 'content-type: multipart/form-data' https://fusion.appdome.com/api/v1/tasks

{ "task_id": ID of the created fuse task }

When you have to renew your API Token to complete builds:

• curl -X POST -H “Authorization:$TOKEN” https://fusion.appdome.com/api/v1/refreshApiToken

The available overrides for the Build task are:

Adding Context to Apps using the Appdome-DEV REST API

After Building your app, you can add context with the pre-configured settings of your selected Fusion Set in the previous step.

-F parent_task_id=<Task ID> //(from the Upload task response)
-F action=context
-F 'overrides={<overrides, or empty JSON>}' //(see details below)
-F icon_overlay_content=@<path/to/single/file>
-F app_customization_application_icon=@<path/to/single/file>
-F app_customization_application_files=@<path/to/single/file>

curl -X POST -H "Authorization: dkG90pp9LPsXUC_pPWO0qA" -F parent_task_id=lix-X4WwvH6joI9DqjdlnQ -F action=context -F 'overrides={}' -H 'content-type: multipart/form-data' https://fusion.appdome.com/api/v1/tasks

{ "task_id": ID of the created fuse task }

The available overrides for the Context task are:

Signing Apps using the Appdome-DEV REST API

Using the Appdome REST API, You can sign your app in three ways:

1. Automatic Singing (Android, iOS) – If you saved your singing credentials in the Fusion Set, you can use this command to sign the app automatically, and receive a signed binary.
2. Private Singing (Android, iOS) – If you want to seal the app, download a non-signed binary and sign it locally.
3. Auto-DEV private Singing (Android, iOS) – The app is sealed and wrapped in a singing script, which you can run to automatically sign the app locally (without uploading the certificates to the platform).

The API request for all the signing tasks are identical, only the action needs to be changed.

• For Automatic Signing use sign
• For Private Signing use seal
• For Auto-DEV Private Signing use sign_script

• NOTE: When signing Android with Private Singing or Auto-DEV Signing, please add the certificate SHA-1 fingerprint as an override: overrides={"signing_sha_fingerprint":"<SHA1-fingerprint or SHA256-fingerprint>"}

Example:
‘overrides={“signing_sha_fingerprint”:”6B:D1:79:F9:5F:7B:BE:64:A3:A5:DC:59:B6:62:E8:67:4F:44:0D:54″}’
or
‘overrides={“signing_sha_fingerprint”:”6BD179F95F7BBE64A3A5DC59B662E8674F440D54″}’

• NOTE: When singing iOS, always add the Form data -F provisioning_profile=@<path/to/file> // (only iOS)

-F parent_task_id=<Task ID> //(from the Upload task response)
-F action=sign //OR
-F action=seal //OR
-F action=sign_script
-F 'overrides={<overrides, or empty JSON>}' //(see details below)
-F provisioning_profile=@<path/to/file> // (only iOS)

curl -X POST -H "Authorization: dkG90pp9LPsXUC_pPWO0qA" -F parent_task_id=lix-X4WwvH6joI9DqjdlnQ -F action=sign -F 'overrides={}' -H 'content-type: multipart/form-data' https://fusion.appdome.com/api/v1/tasks 

curl -X POST -H "Authorization: dkG90pp9LPsXUC_pPWO0qA" -F parent_task_id=lix-X4WwvH6joI9DqjdlnQ -F action=seal -F 'overrides={"signing_sha_fingerprint":"6B:D1:79:F9:5F:7B:BE:64:A3:A5:DC:59:B6:62:E8:67:4F:44:0D:54"}' -H 'content-type: multipart/form-data' https://fusion.appdome.com/api/v1/tasks 

Available overrides for the Signing Task:

Getting the Status of a Task

You can send a GET request to check the status of a task (of the same user). The Task ID is sent in the URL:

curl -X GET -H "Authorization: dkG90pp9LPsXUC_pPWO0qA"  https://fusion.appdome.com/api/v1/tasks/lix-X4WwvH6joI9DqjdlnQ/status

{ "status": Current Task Status}

Download and Deploy Apps using the Appdome-DEV REST API

Once your app is signed or sealed, you can download your enterprise-ready app using the Download GET request. The Task ID is sent in the URL:

OUTPUT_PATH=`echo <apk full path>` && curl -X GET -H "Authorization: dkG90pp9LPsXUC_pPWO0qA" https://fusion.appdome.com/api/v1/tasks/lix-X4WwvH6joI9DqjdlnQ/output --output $OUTPUT_PATH

If you used Automatic Singing, you can also automatically deploy the app using the API. First, make sure you configure the automatic deployment parameters in the Deploy page on the Platform.

To send a deployment request for any type of deployment, other the Apple’s Appstore, use this API request:

curl -X POST -H "Authorization: dkG90pp9LPsXUC_pPWO0qA" -d '{"parent_task_id": "lix-X4WwvH6joI9DqjdlnQ", "action": "deploy"}' -H 'content-type: application/json' https://fusion.appdome.com/api/v1/tasks 

To deploy your app to Apple’s Appstore, due to Apple’s requirements, you can download a script that will perform this from your Mac, using this API. The Task ID is sent in the URL:

curl -X GET -H "Authorization: dkG90pp9LPsXUC_pPWO0qA" -H 'content-type: application/json' https://fusion.appdome.com/api/v1/tasks/lix-X4WwvH6joI9DqjdlnQ/deploy_script 

How Do I Learn More

Check out Appdome Platform, or learn more about Appdome-DEV REST API and Appdome-DEV.

You can also use our API requests Postman Collection.

If you have any questions, please send them our way at support@appdome.com or via the chat window on the Appdome platform.

Thank you!

Thanks for visiting Appdome! Our mission is to make mobile integration easy. We hope we’re living up to the mission with your project. If you don’t already have an account, you can sign up for free.