Launch an agent run
POST
Approve a run's pieces together, the way the app's launch does. start picks when they go out:
suggested(default): each at its suggested time.now: starting now, with the spacing between them kept.all_now: all of them now.launch: the article at its time, with its launch posts.launch_now: the article and its launch posts now, the rest after.
This counts the same as approving in the app. With no entries, it launches every piece of the run that's waiting for approval and not on hold.
apiKeyheader
AuthorizationBearer <token>API key for authenticating protected endpoints. Pass as Bearer token in Authorization header.
agentKey*stringWhich agent, such as changelog
runId*stringThe run to launch
Body
application/json- body
start?stringValue in
"suggested""now""all_now""launch""launch_now"timeZone?stringIANA time zone that launch_now keeps follow-up times of day in. Defaults to UTC
Length
1 <= length <= 64entries?array<>The run's entries to launch, from GET /v1/schedule
Items
1 <= items <= 100200
application/json- response
approved*array<string>Entry ids now scheduled
failed*array<>entries*array<>The run's entries as they now stand
curl -X POST "https://example.com/v1/agents/string/runs/string/launch" \ -H "Content-Type: application/json" \ -d '{}'{ "approved": [ "string" ], "failed": [ { "id": "string", "reason": "string" } ], "entries": [ { "id": "string", "contentId": "string", "kind": "post", "channel": "string", "status": "unplanned", "needsApproval": true, "publishAt": "string", "publishedAt": "string", "failureReason": "string", "holdReason": "string", "accountId": "string", "accountLabel": "string", "entryRevision": 0 } ]}