MoreLogin provides two API access methods. Choose the one that fits your use case.
| Local API | Open API | |
|---|---|---|
| Base URL | http://127.0.0.1:40000 | https://api.morelogin.com |
| Access | Local machine only | Remote, from anywhere |
| Authentication | Optional token (configurable in Settings) | OAuth2 (client_id + client_secret → access_token) |
| Supported Modules | Browser Profiles, Cloud Phones, Proxies, Groups, Tags | Cloud Phones, Proxies, Groups, Tags |
| Best For | Browser automation, local cloud phone management | Remote/server-to-server cloud phone management |
| Requires | MoreLogin desktop app running (v2.15.0+) | API ID and API Key from dashboard |
| Rate Limit | 120 requests/minute | 120 requests/minute |
- You are automating browser profiles (create, start, stop, manage)
- You need Selenium or Puppeteer WebDriver integration
- You want to manage cloud phones from the same machine as MoreLogin (file upload, app management, scheduling, etc.)
- You need to manage proxies, groups, and tags locally
- Your automation script runs on the same machine as MoreLogin
- You need remote access to manage cloud phones from a server
- You are building a server-to-server integration
- You want to manage cloud phones from a CI/CD pipeline
- Your application runs on a different machine than MoreLogin
Yes! Many developers use both APIs:
- Local API for browser profile automation + local cloud phone and shared resource management
- Open API for remote cloud phone and shared resource management (e.g., from a CI/CD pipeline or external server)
Note: For Cloud Phones and Shared Resources, the Local API and Open API provide similar functionality but paths differ. Local API paths use the
/api/prefix (e.g.,/api/cloudphone/page), while Open API paths omit it (e.g.,/cloudphone/page). Some endpoints (e.g., file upload) also have different naming. Always refer to the specific API reference for exact details.