Create task queue briefing schedule
/v1/task-queue/briefing-schedules
Signed-in sessionLaunch key product.workOperation task_queue_briefing_schedule_create
A person puts work in their own queue: a project task (with a priority, a due time and an optional deadline) or a briefing schedule that their agents write.
Headers
- X-Specify-Account-IdstringRequired
- The account the request acts in.
- X-Specify-Service-Tenancy-IdstringRequired
- The service tenancy the request acts in.
Body
- instructionsstring
- priority"high" | "low" | "normal" | "urgent"
- podcastobject
- agentClientIdstring
- leadMinutesnumber
- graceMinutesnumber
- expectedAuthorizationVersionstring
- recurrencestringRequired
- titlestringRequired
- projectIdsstring[]Required
- timezonestringRequired
Returns
- scheduleIdstringRequired
- nextRunAtnull | numberRequired
- timezonestringRequired
- leadMinutesnumberRequired
- graceMinutesnumberRequired
- priority"high" | "low" | "normal" | "urgent"Required
- podcastbooleanRequired
Errors
400, 401, 403, 404, 409, 429 and 503 return {"error": {"code", "message", "correlationId"}}. A call without a valid credential gets 401 before its input is checked, and so does an address that is not an operation: 404 and 400 come only once the credential is accepted. Public operations answer without one.