Build an App/SDK

post

https://fusion.appdome.com/api/v1/tasks#build

This API allows you to build and customize a mobile app or SDK after uploading your files and obtaining an Application ID. Utilizing existing Fusion Sets, this endpoint initiates the build process. After building, the task_id , referred to as the "Appdome Build ID," is required for all subsequent tasks related to this build.

How to Obtain the Application ID:

After successfully uploading your app to the Appdome platform, follow these steps:

Navigate to the sidebar where your app is listed.
The Application ID will be visible next to the app details, and you can copy it directly from there.

Key	Name in Appdome	Value	Notes
`user_agent`	User Agent Customization	Boolean	Must use with `user_agent_value`
`user_agent_value`	User-Agent Header	String
`extended_logs`	Diagnostic Logs	Boolean	Only if enabled for the user.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Query Params

team_id

string

required

Defaults to personal

Personal or team ID

Body Params

action

string

app_id

string

fusion_set_id

string

overrides

string

Fuse overrides enable modification of fusion set options for specific tasks. Learn more here.
Example input: {"extended_logs": true} --- example for Certificate Pinning: {"mitm_host_server_pinned_certs_list":[{"value": {"mitm_host_server_pinned_certs_type": "no_pinning","mitm_host_server_pinned_certs_domain":"{URL}", "mitm_host_server_pinned_certs_file_filename": "{filename}"}}]}

baseline_profile

file

Android only, a baseline profile file in a zip archive

startup_profile

file

Android only, a startup profile file in a zip archive

input_mapping

file

Android only, a minimization or obfuscation mapping file in a txt file

mobile_anti_bot_list[{index}].value.payload_signing_key_app_specific

file

The index assigns each Payload Signing Key to a specific host profile. The first key is always index 0. Additional keys are indexed as 1, 2, 3, etc., for separate host profiles.

mitm_host_server_pinned_certs_list[index].value.mitm_host_server_pinned_certs_file_content

file

The index assigns each Certificate to a specific pinning profile. The first key is always index 0. Additional keys are indexed as 1, 2, 3, etc., for separate host profiles. There is an option to specify the exact host as stated in the original fusion set and it will be overridden by host name instead of index location

Response

200ID of the created fuse task