Skip to main content
POST
Create execution

Authorizations

Authorization
string
header
required

Developer API key from Dashboard → Settings → Developer API

Body

application/json

Either scriptId or automationId must be provided.

deviceId
string
required

Device to run on.

scheduledAt
string
required

ISO 8601 datetime, e.g. 2025-06-01T12:00:00Z

Minimum string length: 1
scriptId
string

Script to run. Either scriptId or automationId is required.

automationId
string

Automation definition ID (see GET /automations). Either scriptId or automationId is required.

Minimum string length: 1
accountId
string

Social account to operate on. It must be linked to this device and match the automation’s platform; its container is snapshotted onto the run so a later reassignment cannot retarget it.

inputValues
object

Keyed by the automation input IDs from GET /automations/{id}. The account_selection input is filled in automatically when accountId is set.

enableAIRecovery
boolean
switchMobileData
boolean

Cycle the phone’s cellular data (off → on) right before the run to get a fresh carrier IP. Only true triggers the cycle.

runtimeProvider
enum<string>

Force the provider for this run. Omit to fall back to the account’s defaultRuntimeProvider, then to inference.

Available options:
doritos,
doritos-lite,
none

Response

Execution created

execution
object
required

Execution with unexpanded relations — scriptId, deviceId, accountId and containerId are UUID strings.

conflicts
object[]
required

Pending runs on the same device whose estimated window overlaps this one. Informational only.