API overview - AutoGrowth

The AutoGrowth API is how you schedule work on your fleet from your own code. It reads the same rows the dashboard reads — phones, accounts, automations, content — and writes the same executions the dashboard writes.

https://api.autogrowth.farm/v1

Every endpoint takes a bearer key and returns JSON. Full field-by-field detail is in the API Reference; this tab is the shape around it.

What it reaches

Resource	You can
Devices	List the phones you can reach, and assign tags or teammates to one
Accounts	List, read, pause and resume your social accounts, and read their scraped follower history
Automations	Read the built-in catalog and each automation’s inputs
Scripts	Read your scripts, including their node graph
Executions	Schedule runs one at a time or 100 at a time, list them, cancel and delete them
Content	Upload media, list it, star it, delete it, and check storage usage
Collections	Create, update and delete collections, and move content in and out
Prompts	Full create, read, update and delete
Tags	List the organization’s tags
Stats	The dashboard’s aggregate counters

What it does not reach

The live screen and remote control. Both are dashboard-only, over WebSocket and MJPEG. There is no API for either.
The Companion. Nothing in the API installs, starts or configures the desktop app, and nothing runs while it is closed.
Script authoring. Scripts are read-only here, and the Script Builder is locked platform-wide.
Billing. Buying slots, credits or Autogrowth MAX happens in the dashboard.

Quickstart

Create a key

In the dashboard, open Settings → Developer API and create a key. It is shown once — copy it into your secret manager immediately. You need the Manage API keys permission to see that screen. Details in Authentication.

List your phones

curl https://api.autogrowth.farm/v1/devices \
  -H 'Authorization: Bearer a1b2...replace-with-your-key'

const res = await fetch('https://api.autogrowth.farm/v1/devices', {
	headers: { Authorization: `Bearer ${process.env.AUTOGROWTH_API_KEY}` },
});
const { devices } = await res.json();
for (const device of devices) {
	console.log(device.id, device.name, device.online, device.slotState);
}

import os, requests

res = requests.get(
	"https://api.autogrowth.farm/v1/devices",
	headers={"Authorization": f"Bearer {os.environ['AUTOGROWTH_API_KEY']}"},
)
for device in res.json()["devices"]:
	print(device["id"], device["name"], device["online"], device["slotState"])

Note the id of a phone whose slotState is active. A phone with an expired slot cannot be scheduled on.

Schedule a run

Automation IDs come from GET /automations, which also returns each automation’s inputs. Keys in inputValues are those inputs’ id fields.

curl -X POST https://api.autogrowth.farm/v1/executions \
  -H 'Authorization: Bearer a1b2...replace-with-your-key' \
  -H 'Content-Type: application/json' \
  -d '{
    "automationId": "warmup-instagram",
    "deviceId": "0198f8a0-1111-7aaa-8ccc-3e5d7c9b1a24",
    "scheduledAt": "2026-09-01T14:00:00Z",
    "inputValues": { "account": "yourhandle", "duration": "30" }
  }'

const res = await fetch('https://api.autogrowth.farm/v1/executions', {
	method: 'POST',
	headers: {
		Authorization: `Bearer ${process.env.AUTOGROWTH_API_KEY}`,
		'Content-Type': 'application/json',
	},
	body: JSON.stringify({
		automationId: 'warmup-instagram',
		deviceId: deviceId,
		scheduledAt: '2026-09-01T14:00:00Z',
		inputValues: { account: 'yourhandle', duration: '30' },
	}),
});
if (!res.ok) throw new Error((await res.json()).error);
const { execution, conflicts } = await res.json();

import os, requests

res = requests.post(
	"https://api.autogrowth.farm/v1/executions",
	headers={
		"Authorization": f"Bearer {os.environ['AUTOGROWTH_API_KEY']}",
		"Content-Type": "application/json",
	},
	json={
		"automationId": "warmup-instagram",
		"deviceId": device_id,
		"scheduledAt": "2026-09-01T14:00:00Z",
		"inputValues": {"account": "yourhandle", "duration": "30"},
	},
)
res.raise_for_status()
execution = res.json()["execution"]

A 201 means the run is queued, not that it has happened. Poll GET /executions for its status, or read it back by ID.The response also carries conflicts: pending runs on the same phone whose window overlaps this one. It is information, not a rejection — the phone runs one execution at a time and queues the rest.

Running an automation requires Autogrowth MAX. Without it, POST /executions answers 403 with the code MAX_REQUIRED. Listing the catalog works either way.

Before you build

Authentication

Key format, the bearer header, and the scoping rule that surprises everyone.

Conventions

IDs, timestamps, dropped nulls, expanded references, no pagination.

Errors

The error envelope, the codes, and what to do about each.

API Reference

Every endpoint, generated from the spec.

​What it reaches

​What it does not reach

​Quickstart

​Before you build

Authentication

Conventions

Errors

API Reference

What it reaches

What it does not reach

Quickstart

Before you build