API reference
Create a disabled pilot schedule
POST /v1/pilot/schedules
Requires sync:write. Requires an active connection and destination, both runtime grants and homogeneous published timezone evidence. windowDays is 1–31 and cadenceMinutes is 60 or 1440. The service assigns next_due_at from its current time. Every successful creation creates a new disabled schedule; retain scheduleId. One schedule per destination may later be enabled. Implemented and locally tested; new live scheduled delivery and controlled failure/recovery acceptance remain pending.
Authorizations
Section titled “Authorizations ”Request Body required
Section titled “Request Body required ”Exactly these fields; workspace comes from the current API key and timezone from existing homogeneous published heads. No arbitrary timezone, token, spreadsheet ID or due time is accepted. Cadence options do not imply billing enforcement.
object
Responses
Section titled “ Responses ”Create a disabled pilot schedule.
object
A timezone accepted by the runtime IANA timezone formatter; selected from homogeneous published source heads.
invalid_json, invalid_request, or invalid_schedule for an unsupported cadence/window.
object
object
object
object
Missing, expired, revoked or reassigned key, including changes before response release.
object
object
object
object
Headers
Section titled “Headers ”forbidden, source_permission_required, or destination_permission_required.
object
object
object
object
connection_unavailable or destination_not_found in this workspace.
object
object
object
object
method_not_allowed — use the method named in Allow.
object
object
object
object
Headers
Section titled “Headers ”destination_unavailable, timezone_unverified, timezone_conflict, schedule_conflict, or sheet_capacity_exhausted.
object
object
object
object
Request JSON exceeds 4096 bytes.
object
object
object
object
Use application/json with no Content-Encoding other than identity.
object
object
object
object
automation_unavailable.