Confirm a deferred schedule as the account owner

Requires the owner's own plori_sk_ API key or OAuth access token outside MCP. Takes no body. Changes awaiting_confirmation to pending and records confirmed_at only while fire_at is in the future. An already confirmed row returns 200 unchanged. MCP requests receive 403 with the confirmation link in the error text.

post/v1/agents/{agentID}/schedules/{scheduleID}/confirm

Request

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

Path parameters

agentIDstring uuid required
scheduleIDstring uuid required

Response

Schedule confirmed, or already confirmed (idempotent).

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.