Skip to main content

​
Maintenance Guide

Phonefarm maintenance is an account-first process family for upkeep tasks rather than content posting or warmup execution. Use: 
POST /maintenance/requests

​
What Maintenance Supports Today

Currently implemented:
  • edit_profile
Currently not documented as public:
  • other planned maintenance composites or unsupported steps

​
Example Edit Profile Workflow

  1. Create a maintenance process with one or more edit_profile steps.
  2. Receive the accepted callback.
  3. Poll the process record for current status.
  4. Cancel the process if needed with process-aware cancel.

​
Example Payload

{
  "request_id": "maint-2026-03-22-001",
  "account_id": "account_user095916355",
  "inputs": {
    "steps": [
      {
        "action": "edit_profile",
        "params": {
          "display_name": "weekday meals",
          "bio": "quick dinners and meal prep",
          "username": "easymealsdaily",
          "mutation_kind": "operator_requested",
          "randomized": false
        }
      }
    ],
    "metadata": {
      "source": "ugc-tracker"
    }
  },
  "callback": {
    "url": "https://ugc-tracker.example.com/phonefarm/process-updates",
    "metadata": {}
  },
  "requested_by": {
    "system": "ugc-tracker",
    "user": "operator@example.com",
    "metadata": {}
  }
}

​
Step Rules

  • action must be edit_profile
  • at least one of display_name, bio, or username must be present
  • mutation_kind and randomized are optional execution metadata fields

​
Best Practices

  • Use one clear request_id per operator intent.
  • Keep profile edits explicit and minimal.
  • Treat the returned process record as the canonical lifecycle object.