Schedule a deferred one-shot run

A direct owner session using the owner's plori_sk_ API key or OAuth access token outside MCP creates a pending schedule. An MCP request creates an awaiting_confirmation schedule with confirm_url. It cannot fire until the owner confirms. Unconfirmed rows have no expiry sweep.

post/v1/agents/{agentID}/schedules

Request

  • Base URL: https://api.plori.ai
  • URL: https://api.plori.ai/v1/agents/{agentID}/schedules
  • Auth: HTTP bearer

Path parameters

agentIDstring uuid required

Request body

promptstring required
fire_atstring date-time

RFC3339 UTC. Exactly one of fire_at or delay_seconds.

delay_secondsinteger
session_idstring

Pin the thread; omit for the agent's active thread.

metadataobject

Response

Schedule created.

idstring uuid
agent_idstring uuid
kind'once'
status'awaiting_confirmation' | 'pending' | 'firing' | 'dispatched' | 'done' | 'cancelled' | 'failed'

AI-client-created schedules await owner confirmation. done does not establish task success; inspect the run outcome.

promptstring
fire_atstring date-time
thread_idstring
metadataobject
last_errorstring
attemptsinteger
created_atstring date-time
last_fired_atstring date-time
confirmed_atstring date-time

Time the owner confirmed the schedule. Absent when unset.

confirm_urlstring uri

Owner confirmation page. Present only for awaiting_confirmation schedules.

Changes

No recorded changes to this operation across all 1 revision of this API.