Delete a schedule
Destructive. A DELETE without the body { confirm: true } answers 400 confirmation_required with the consequences and the re-send form. With confirm the schedule record is removed, all future scheduled scans stop, and the setup stays usable for manual scans (historical scans keep their own records and billing).
/schedules/{schedule_id}AuthorizationBearer token · headerrequiredAPI key sent as Authorization: Bearer <key>. A key belongs to one workspace, has scopes, and can be limited to some brands.
AuthorizationOAuth2 access token · headerrequiredOAuth 2.1 sign-in (authorization code with PKCE) used by AI assistants that connect through the Zaraftis MCP server. Discovery URLs are at https://api.zaraftis.com/api/auth.
schedule_idstring<uuid>requiredapplication/jsonconfirmbooleanrequiredThe removed schedule reference
ScheduleDeletedEnvelopebad_request or validation_failed
successbooleanrequirederrorobjectrequiredShow propertiesHide properties
codestringrequiredmessagestringrequiredretryablebooleanrequireddetailsobjectfield_errorsobject[]Show propertiesHide properties
objectfieldstringrequiredcodestringrequiredrequiredformattoo_smalltoo_largeunrecognized_keyinvalidmessagestringrequiredrequest_idRequestIdrequirednot_found: unknown id, or an id this key cannot see
successbooleanrequirederrorobjectrequiredShow propertiesHide properties
codestringrequiredmessagestringrequiredretryablebooleanrequireddetailsobjectfield_errorsobject[]Show propertiesHide properties
objectfieldstringrequiredcodestringrequiredrequiredformattoo_smalltoo_largeunrecognized_keyinvalidmessagestringrequiredrequest_idRequestIdrequired