Loading the fleet

Checking workers and phones.

Show screens

Workers

Ready Running an action Booting On an unknown screen

Loading workers.

Deleted phones 0

Phone	Account	Android	Worker	Last screen	Final message	Deleted
No deleted phones yet.

Logs and unknown pages

Read from the MariaDB tables Emulators_UnknownPages and Emulators_ActionLogs.

Unknown pages and action errors

ID	Phone	Account	Action	Screen	Reason	When	Screen dump
Loading.

Recent logs

ID	Level	Event	Phone	Action	Page	Message	When
Loading.

Quick start

Everything goes through this manager. Launch a phone, start an action on it, then poll until the action finishes. Phones run on worker droplets, but you never call a worker directly.

Loading examples.

OpenAPI JSON Swagger UI in a new tab

Automation actions

Start an action with POST /api/emulators/{emu_id}/actions, then poll GET /api/emulators/{emu_id}/actions/{action_id} until its state is COMPLETED or FAILED.

Endpoints

Every route the manager serves, grouped by what it is for. Open a row for details and an example body.

Phone locations

The manager tracks which Snapchat screen each phone is on, so back-to-back actions can start without restarting the app.

Location	Meaning

API explorer

Try any endpoint here. Requests sent from the explorer run against the live cluster.