v1
schedules

List copilot follow-up schedules for a user

Changed on

Return only copilot-turn schedules for the current user.

Sibling of :func:list_all_graphs_execution_schedules; one route per kind keeps the generated frontend client typed to a single concrete return type instead of a discriminated union.

get/api/schedules/followups

Request

  • The document declares no server URL.
  • Auth
    HTTP bearer

Response

Successful Response

kind'copilot_turn'
schedule_idstring nullable
user_idstring required
session_idstring nullable
messagestring required
cronstring nullable
run_atstring date-time nullable
cap_retry_countinteger
expert_lookup_retry_countinteger
plan_lookup_retry_countinteger
limits_retry_countinteger
usage_wait_countinteger
user_timezonestring nullable
organization_idstring nullable
team_idstring nullable
expert_idstring nullable
routine_idstring nullable
routine_schedule_idstring nullable
credential_pinsobject
purpose'followup' | 'resume' | 'send'
created_atstring date-time nullable
idstring required
namestring required
next_run_timestring required
timezonestring

Timezone used for scheduling

Changes

    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status