Automations

One automation drives exactly one TikTok account per firing. Posting to multiple accounts means multiple automations — matching how the product’s own predictable-credit-spend model works.

Create an automation

string

required

string

required

"slideshow" | "hook_video"

array

required

[{ "time": "09:00", "days": ["mon", "wed", "fri"] }] — 24h time, lowercase 3-letter days.

string

required

object

Same shape as content brief.

string

default:"manual"

"auto" | "manual". Manual means every firing lands as pending content requiring approval — the safe default.

string

default:"drafts"

"drafts" | "publish". "publish" requires the creating key to have schedules:publish.

Requires automations:write.

curl -X POST https://www.try-orbit.com/api/v1/automations \
  -H "Authorization: Bearer $STRATOS_API_KEY" -H "Content-Type: application/json" \
  -d '{
    "appId": "product_a1b2c3",
    "format": "slideshow",
    "postingTimes": [{"time": "09:00", "days": ["mon","wed","fri"]}],
    "tiktokAccountId": "...",
    "brief": {"topic": "app growth tips"},
    "approvalMode": "manual"
  }'

List / get / update / delete

GET /v1/automations — automations:read
GET /v1/automations/{id} — automations:read
PATCH /v1/automations/{id} — automations:write. Body: { "status": "active" | "paused", "postingTimes"?, "brief"? }
DELETE /v1/automations/{id} — automations:write

Automations created via this API are stored in a v1_automations table separate from the app’s own automations table — the scheduler that actually fires them needs a follow-up integration pass to read both. Check GET /v1/automations/{id} for status; if firings aren’t happening yet in your deployment, this is why.

Getting Started

Guides

API Reference

Create an automation

List / get / update / delete

​Create an automation

​List / get / update / delete

Create an automation

List / get / update / delete