VMOS & Redfinger API Automation

VMOS Cloud and Redfinger sit in the budget tier of cloud phones — popular for TikTok warm-up, test accounts, and teams learning mobile ops before committing to GeeLark or DuoPlus. API shape is similar: pad/instance ID → start session → ADB or vendor SDK → stop to save minutes.

When VMOS/Redfinger vs premium vendors

VMOS Cloud API pattern

# Illustrative — verify official VMOS developer docs
POST /api/v1/pad/create     → pad_id, android_version
POST /api/v1/pad/{id}/start → status, adb_host, adb_port, expire_at
POST /api/v1/pad/{id}/stop  → billing stop

# Proxy: often set at create or via dashboard before start
{
  "pad_id": "pad-8842",
  "proxy": {"type": "socks5", "host": "...", "port": 1080, "user": "...", "pass": "..."}
}

Redfinger API pattern

• Session-based billing — stop pad immediately after job; idle = cost leak
• Region nodes — pick node closest to proxy geo (EU proxy → EU node)
• Root vs non-root — some apps detect root; use non-root SKU for TikTok/IG prod
• Reconnect — ADB drops after idle; wrap jobs with adb reconnect retry

Python worker with tier routing

import asyncio
import httpx

TIER_VENDOR = {
    "burn": "vmos",       # cheap warm / disposable
    "warm": "redfinger",  # mid tier
    "prod": "geelark",    # route prod to premium API (see other guide)
}

async def run_pad(vendor: str, pad_id: str, job):
    cfg = VENDOR_BASE[vendor]  # your config map
    async with httpx.AsyncClient(timeout=120) as client:
        start = await client.post(f"{cfg['base']}/pad/{pad_id}/start", headers=cfg["headers"])
        start.raise_for_status()
        adb = start.json()["adb_endpoint"]
        try:
            await job(adb)
        finally:
            await client.post(f"{cfg['base']}/pad/{pad_id}/stop", headers=cfg["headers"])

async def route_account(account_row: dict):
    vendor = TIER_VENDOR[account_row["tier"]]
    await run_pad(vendor, account_row["pad_id"], warm_up_tiktok)

Health gates (budget tier)

1. Play Integrity / SafetyNet — higher fail rate on budget SKUs; track per pad_id
2. adb shell getprop ro.build.tags — test-keys vs release-keys
3. IP geo vs account CMDB — budget pools often share egress; avoid cross-geo logins
4. Session timer — cron stop all pads nightly to prevent billing drift

Graduation path

When ban rate on VMOS/Redfinger exceeds your threshold for a client tier, migrate pad to GeeLark/DuoPlus without changing account credentials — update CMDB cloud_device_id only. See GeeLark & DuoPlus API guide and troubleshooting runbook.

Related

Disclosure: MLX-MMO affiliated with Multilogin. VMOS and Redfinger API paths are illustrative — confirm with official vendor documentation.