canonical: https://jentic.com/apis/api.morelogin.com/morelogin

# MoreLogin Open API

Jentic publishes the only available OpenAPI specification for MoreLogin Open API, keeping it validated and agent-ready. MoreLogin is a mobile automation platform powered by cloud-based Android devices that lets teams operate hundreds of isolated Android profiles for testing and automation. The API exposes 21 endpoints covering OAuth token issuance, cloud phone profile lifecycle, file upload to a profile, app installation, schedule management, proxy assignment, and group and tag organisation. It is suited for QA fleets, mobile bot operations, and any workflow that requires programmatic control of disposable Android profiles.

## For AI agents

Operate MoreLogin cloud-based Android profiles: list and create profiles, start and stop them, install apps, upload files, manage proxies, and organise profiles via groups and tags.

## Scope

Does not handle iOS device automation, in-app billing analytics, or human verification - use for Android cloud phone profile lifecycle and automation only.

## Capabilities

- Issue an OAuth access token to authenticate downstream calls against MoreLogin
- Create, list, start, stop, and delete cloud phone profiles on demand
- Upload files into a running cloud phone and list its existing files
- Install apps onto a cloud phone profile and list installed apps
- Create schedules and list scheduled jobs that act on cloud phones at fixed times
- Manage proxies - list, create, and delete - and assign them to profiles for traffic routing
- Organise cloud phones via groups and tags for bulk operations and reporting

## Use cases

### Mobile QA Test Farm

Run mobile QA suites in parallel by spinning up disposable cloud phone profiles, installing the build under test, executing the suite, and tearing the profiles down. The API exposes /api/cloudphone/create, /api/cloudphone/start, /api/cloudphone/app/install, and /api/cloudphone/delete to drive the lifecycle. Most teams build the orchestration in 3 to 5 days.

Example prompt: Create 10 cloud phones in group 'qa-fleet', start each one, install the APK at https://builds.example.com/app-2.4.1.apk via /api/cloudphone/app/install, and after the test job tag them with the build version.

### Scheduled Mobile Automation Jobs

Operate mobile automation tasks (data scraping, account warm-up, app review monitoring) on a schedule using /api/cloudphone/schedule/create. The platform handles starting and stopping cloud phones at the configured times so the orchestrator does not need to keep a long-running process. Setup is typically a day for a basic schedule plus reporting.

Example prompt: Call /api/cloudphone/schedule/create to start cloud phones 4421 and 4422 every weekday at 09:00 UTC and stop them at 18:00 UTC.

### Proxy-Routed Cloud Phones

Assign per-profile proxies via /api/proxy/create and the cloud phone profile create payload to route each Android profile through a different IP. This is essential for multi-account testing and fingerprint isolation. Proxy management plus profile assignment is normally built in two days.

Example prompt: Create a residential proxy via /api/proxy/create, then create 5 cloud phone profiles via /api/cloudphone/create each referencing the new proxy ID.

### AI Agent Mobile Operator

An AI agent can drive a fleet of MoreLogin Android profiles to validate user-facing app changes, collect screenshots, and attach them to a Jira ticket. Through Jentic, the OAuth token lives in your Jentic One instance and the agent calls cloud phone operations by intent. Setup is under an hour.

Example prompt: Use Jentic to search for 'create and start an Android cloud phone', execute /api/cloudphone/create followed by /api/cloudphone/start, install the APK, and capture screenshots before tearing the profile down.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/oauth/token | Issue an OAuth access token |
| POST | /api/cloudphone/create | Create a cloud phone profile |
| POST | /api/cloudphone/start | Start a cloud phone |
| POST | /api/cloudphone/stop | Stop a cloud phone |
| POST | /api/cloudphone/app/install | Install an app on a cloud phone |
| POST | /api/cloudphone/file/upload | Upload a file to a cloud phone |
| POST | /api/proxy/create | Create a proxy |
| POST | /api/cloudphone/schedule/create | Create a schedule for cloud phones |

## Key resources

- **Authentication** — Issue OAuth access tokens for downstream calls
- **Cloud Phones** — Create, list, start, stop, and delete cloud phone profiles
- **Files** — Upload files into a profile and list its existing files
- **Apps** — Install apps on a profile and list installed apps
- **Schedules** — Create and list schedules that start and stop cloud phones at fixed times
- **Proxies** — List, create, and delete proxies assigned to cloud phone profiles
- **Groups and Tags** — Organise cloud phones for bulk operations and reporting

## Why Jentic

- **Setup:** Wiring the MoreLogin Open API by hand means exchanging credentials at its oauth/token endpoint for a bearer token and coding your own calls to the cloud phone lifecycle endpoints. Through Jentic you install once, import the MoreLogin Open API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** MoreLogin cloud phone and app targets travel in the request body rather than as ids in the URL path, so limit the agent to the operations it needs, such as creating and starting a cloud phone, and leave app install or file upload out of the allowed set. Every operation you grant is your explicit choice.
- **Credential handling:** Your MoreLogin credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a cloud phone profile' or 'start a cloud phone', and Jentic returns the matching MoreLogin operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **GitHub API** — Source-control and CI provider that triggers QA runs on MoreLogin profiles
- **Pipefy API** — Workflow platform for routing QA results into approval pipelines
- **SmartRecruiters API** — ATS for managing QA staffing and contractor onboarding

## FAQ

### Why is there no official OpenAPI spec for MoreLogin Open API?

MoreLogin does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MoreLogin Open API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the MoreLogin Open API use?

MoreLogin uses HTTP bearer authentication. Call POST /api/oauth/token with your client credentials to issue a bearer token, then send it on every subsequent request. Through Jentic, those credentials live encrypted in your Jentic One instance - the agent never sees the raw client secret.

### Can I install an APK on a cloud phone with the MoreLogin Open API?

Yes. POST /api/cloudphone/app/install installs an APK referenced by URL or upload onto a specific cloud phone profile. List currently installed apps via GET /api/cloudphone/app/list.

### What are the rate limits for the MoreLogin Open API?

MoreLogin does not publish a public rate limit policy. Limits are tied to your subscription tier - contact MoreLogin support to confirm the per-second and per-day caps that apply to your client ID.

### How do I create and start a cloud phone with the MoreLogin Open API through Jentic?

Run pip install jentic, then search for 'create and start an Android cloud phone'. Jentic returns the /api/cloudphone/create and /api/cloudphone/start operation schemas. Execute create first, then poll start until the profile reports ready.

### Does the MoreLogin Open API support per-profile proxies?

Yes. GET /api/proxy/list, POST /api/proxy/create, and POST /api/proxy/delete manage proxies. When creating a cloud phone profile, reference the proxy ID so traffic from that Android profile is routed through it.

### Can I limit what my agent is allowed to do with the MoreLogin Open API?

Yes. Because you run Jentic One yourself, your own rules decide which MoreLogin operations and credentials the agent may use. You can grant only the operations it needs, such as POST /api/cloudphone/create and POST /api/cloudphone/start, and leave POST /api/cloudphone/app/install and POST /api/cloudphone/file/upload out of the allowed set. Since the cloud phone and app targets travel in the request body rather than the URL path, every operation the agent can call is your explicit choice.