Skip to main content
POST
Create Loop

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

team_id
string<uuid>
required

Body

application/json
name
string
required
Required string length: 1 - 255
agent_member_id
string<uuid>
required
task_type
string
required
Minimum string length: 1
phase
string | null
parent_loop_id
string<uuid> | null
schedule_type
enum<string>
default:cadence
Available options:
cadence,
specific_days,
signal_triggered
cadence
LoopCadence · object
task_template
Task Template · object
priority
enum<string>
default:medium
Available options:
critical,
high,
medium,
low
sort_order
integer
default:0
content_source
ContentSourceConfig · object | null

Per-loop content-driven source config (SMMT content-driven distribution).

Typed (not a raw dict) so malformed payloads are rejected at the API boundary with a 422 rather than persisting silently and never dispatching: cycle_scheduler._loop_content_source() only treats a loop as content-driven when content_source is a dict carrying a non-blank source_url, so an invalid value would look "saved" but quietly stop distribution. source_type is auto-detected at scan time; tag/recency rules are consumed by content_source_scanner.pick_next_item.

Response

Successful Response

id
string<uuid>
required
cycle_id
string<uuid>
required
parent_loop_id
string<uuid> | null
required
name
string
required
agent_member_id
string<uuid>
required
phase
string | null
required
schedule_type
string
required
cadence
Cadence · object
required
task_type
string
required
task_template
Task Template · object
required
priority
string
required
sort_order
integer
required
is_active
boolean
required
created_at
string<date-time>
required
updated_at
string<date-time>
required
content_source
ContentSourceConfig · object | null

Per-loop content-driven source config (SMMT content-driven distribution).

Typed (not a raw dict) so malformed payloads are rejected at the API boundary with a 422 rather than persisting silently and never dispatching: cycle_scheduler._loop_content_source() only treats a loop as content-driven when content_source is a dict carrying a non-blank source_url, so an invalid value would look "saved" but quietly stop distribution. source_type is auto-detected at scan time; tag/recency rules are consumed by content_source_scanner.pick_next_item.