Phonefarm
Phonefarm is externally triggered TikTok execution infrastructure. Upstream systems such as UGC Tracker submit work, Phonefarm materializes that work onto phones, and callers observe normalized process state through callbacks and polling.Who These Docs Are For
- Teams integrating Phonefarm into another product or control plane.
- Agents that need exact request and response contracts.
- Engineers who need to understand process lifecycle, callbacks, idempotency, and capability constraints.
What Phonefarm Is
- A process-oriented execution API.
- A capability runner for
keyword_warmup,fyp_warmup, andmaintenance. - A normalized process-status layer over richer internal queue and runtime mechanics.
What Phonefarm Is Not
- Not a content generation system.
- Not a scheduler that invents work on its own for external callers.
- Not a public control plane for low-level worker internals.
Official Integration Model
The primary public abstraction is the process API:- Create work with
POST /capability-requests/enqueueorPOST /maintenance/requests. - Receive
process.updatedcallbacks on key milestones. - Poll
GET /processes/{process_id}for source-of-truth state. - Cancel with
POST /processes/{process_id}/cancelwhen needed.
POST /ingestPOST /cancel
Base URLs
- Public API base URL:
https://phonefarm.withmithras.com - Public docs base URL:
https://docs.withmithras.com
Current Public Capabilities
keyword_warmupfyp_warmupmaintenance
Important Caveats
fyp_warmupis currently blocked for unattended use.- Callbacks are best-effort delivery.
GET /processes/{process_id}is the source of truth. - Public statuses are normalized views over richer internal states.
- Public timestamps are milestone-derived and should not be treated as precise device-action timestamps.