Skip to content
Last updated

Manage anti-detection browser profiles programmatically through the MoreLogin Local API.


Overview

The Browser API allows you to create, launch, and control browser profiles with unique fingerprints. It's designed for automation scenarios like multi-account management, web scraping, and automated testing.

Base URL: http://127.0.0.1:40000

The Local API runs on your machine alongside the MoreLogin desktop app. All requests must originate from the same machine.


Capabilities

ResourceDescriptionKey Operations
Browser ProfileAnti-detection browser instancesCreate, start, stop, delete, modify, check status
ProxyProxy configurations for profilesAdd, update, delete, list proxies
GroupOrganize profiles into groupsCreate, edit, delete groups
TagLabel profiles with tagsCreate, edit, delete tags

Quick Example

Create and start a Chrome browser profile:

# 1. Create a profile
curl -X POST "http://127.0.0.1:40000/api/env/create/quick" \
  -H "Content-Type: application/json" \
  -d '{"browserTypeId": 1, "operatorSystemId": 1, "quantity": 1}'

# 2. Start the profile (use envId from step 1)
curl -X POST "http://127.0.0.1:40000/api/env/start" \
  -H "Content-Type: application/json" \
  -d '{"envId": "YOUR_ENV_ID"}'

After starting, you receive:

  • Debug port — for Selenium/Puppeteer connection
  • WebDriver path — for browser automation

Automation Integration

Selenium

from selenium import webdriver

options = webdriver.ChromeOptions()
options.debugger_address = "127.0.0.1:DEBUG_PORT"
driver = webdriver.Chrome(
    executable_path="WEBDRIVER_PATH",
    options=options
)
driver.get("https://example.com")

Puppeteer

const puppeteer = require('puppeteer');

const browser = await puppeteer.connect({
  browserWSEndpoint: 'ws://127.0.0.1:DEBUG_PORT'
});
const page = await browser.newPage();
await page.goto('https://example.com');

Requirements

  • MoreLogin desktop app v2.15.0+ installed and running
  • Logged in to your MoreLogin account
  • Requests must originate from the local machine

Note: The Local API also supports Cloud Phone management endpoints. For Cloud Phone operations, we recommend using the Open API for remote access capability.

For authentication details, see Authentication.