Create one or more cloud phones without setting them up manually.

You can configure values such as:

• Phone name
• Android version
• Phone brand and model
• Proxy
• Notes and tags
• Network and location settings

A proxy is required when you create a cloud phone.

💡 Why it helps: create many cloud phones with the same setup without repeating the same configuration in the dashboard.

The request starts one or more cloud phones without a graphical interface. This is useful for automated workflows that do not need the live phone screen.

The request stops one or more cloud phones. Also useful for automation workflows.

You can update a cloud phone's configuration, including its phone brand and model, title, proxy, notes, tags, and network type. You will need the cloud phone ID, which you can get in the Multilogin dashboard or with GET Mobile Profile List.

💡 Why it helps: It saves time on bulk updates, so you do not need to edit each cloud phone manually in the dashboard.

Remove cloud phones by their IDs. Use this carefully if you automate cleanup workflows.

💡 Why it helps: It lets you remove multiple cloud phones as part of an automated cleanup workflow. This can help free up space under your plan when you need to create new cloud phones.

Use this request to get the cloud phones in your workspace.

The response gives you the cloud phone ID and setup details such as device, location, network, proxy, and workspace information.

💡 Why it helps: many other requests need a cloud phone ID. Start here when you do not have it yet.

Bearer (or automation) token is enough to run the request.

Displays several cloud phone status values, including launch status, runtime, auto-stop timestamp, and ADB status.

💡 Why it helps: It lets you monitor cloud phone status during automation, especially when profiles are started without the GUI.

The endpoint returns the cloud phone group (workspace) or creates a new one. 

💡 Why it helps: It confirms that you are connected to the correct workspace before you continue.

You can apply up to 10 tags at once. Tags are shared between browser profiles and cloud phones. To find a tag, use POST Tag Search endpoint. You will also need the cloud phone ID.

💡 Why it helps: It makes it easier to organize cloud phones automatically and keep larger profile sets easier to manage.

As with tag assignment, you can remove up to 10 tags at once. Tags are shared between browser profiles and cloud phones. You can refer to the tag-related API requests in the profile management folder, e.g. POST Tag Search. Cloud phone ID is also required.

💡 Why it helps: It helps keep your cloud phone organization up to date by removing tags you no longer need.

Returns the list of applications from the app marketplace. The response gives you the app ID and version IDs. You will need these values for app installation.

💡 Why it helps: It gives you the app and version IDs required for automated app installation.

The endpoint installs an app in batch on a group of cloud phones. Use the app ID and the version ID. It installs the app in the default folder. You can also use the endpoint GET Mobile Profile Group Get or Create.

💡 Why it helps: It lets you install the same app on multiple cloud phones without setting up each phone manually.

Get files stored in the library. The response includes file IDs, which you need for file-related requests.

Upload a file to the cloud phone library. You can then use the uploaded file in your mobile workflows.

Note: you can browse for files in Postman.

💡 Why it helps: It lets you add files to the Library automatically so your cloud phones can access them during workflows.

Delete one or more Library files by their file IDs. Get the IDs first with GET Mobile File List.

💡 Why it helps: It makes it easier to clean up Library files automatically when they are no longer needed.

You can apply up to 10 tags at once. Tags are the same as for browser profiles and cloud phones. You can refer to the tag-related API requests in the profile management folder, e.g. POST Tag Search. File ID is also required (GET Mobile File List).

💡 Why it helps: It helps you organize Library files automatically, especially when you manage many uploaded files.

Remove tags from a Library file. Tags are the same as for browser profiles and cloud phones. You can refer to the tag-related API requests in the profile management folder, e.g. POST Tag Search. File ID is also required (GET Mobile File List).

💡 Why it helps: It helps keep Library files organized by removing tags that are no longer relevant.

The request exports cloud phone data to an .xlsx file. You can export up to 200 cloud phones at once.

Note: The result is presented as a file. If you use Postman, click the three-dot menu (near the “Save Response” button) and click “Save response to file”.

💡 Why it helps: It saves time when you need cloud phone data for reporting, backup, or bulk workflows.

Download an import template

Downloads an .xlsx template for bulk cloud phone import. Fill in the data, then validate the file using the following endpoint: POST Import File Validate

Note: The result is presented as a file. If you use Postman, click the three-dot menu (near the “Save Response” button) and click “Save response to file”.

💡 Why it helps: It gives you the correct file structure for bulk cloud phone import, which helps reduce formatting mistakes.

Validate an import file

Check your .xlsx import file before using it.

You can build the file from:

• POST Mobile Profile Export
• GET Import Template Download

💡 Why it helps: validation helps avoid errors during bulk import.

This request lets you transfer profiles to another team member in your workspace. You can transfer up to 200 profiles at once (your current plan limits also apply).

💡 Why it helps: useful when you move cloud phones between team members or reorganize ownership.

Check your workspace's cloud phone minute allowance.

The response shows your total available minutes, how many minutes you have already used, and how many are still remaining.

The request tests the availability of a proxy and provides additional information, like IP, geolocation, timezone, and ISP.

💡 Why it helps: It lets you test a proxy before using it with a cloud phone, which helps catch connection or location issues early.

Use the country code to get the list of states. You can use them for cloud phone creation.

💡 Why it helps: It gives you valid state or region values to use when setting cloud phone location data.

The request returns a list of cities by state or region. You can use the state values from that endpoint: GET States by Country.

💡 Why it helps: It gives you valid city values to use when setting cloud phone location data.

Get supported phone brands and models for an Android version. Use the returned values when you customize cloud phone creation.

💡 Why it helps: It gives you supported brand and model values, so you can use valid device settings when creating cloud phones.