Create execution
Schedules a script or automation to run on a device. Overlapping runs are allowed — a device runs one execution at a time and queues the rest — so any overlap comes back as soft conflicts info rather than a rejection. Automations require an Autogrowth MAX subscription, and the create-account automation additionally requires its paid add-on.
Authorizations
Developer API key from Dashboard → Settings → Developer API
Body
Either scriptId or automationId must be provided.
Device to run on.
ISO 8601 datetime, e.g. 2025-06-01T12:00:00Z
1Script to run. Either scriptId or automationId is required.
Automation definition ID (see GET /automations). Either scriptId or automationId is required.
1Social 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.
Keyed by the automation input IDs from GET /automations/{id}. The account_selection input is filled in automatically when accountId is set.
Cycle the phone’s cellular data (off → on) right before the run to get a fresh carrier IP. Only true triggers the cycle.
Force the provider for this run. Omit to fall back to the account’s defaultRuntimeProvider, then to inference.
doritos, doritos-lite, none