Delete a scan schedule

DELETE 
/api/v1/projects/:project_id/schedules/:schedule_id

Remove a schedule. Past occurrences and created runs are untouched (the occurrence ledger is the audit trail).

Neither flag- nor entitlement-gated: a downgraded org must still be able to turn off what it configured while it was paying. Stopping a schedule from FIRING after a downgrade is a separate product decision, not a side effect of the delete gate.

• Scope required: projects:update + manager-or-above.
• Archived projects reject the write (409).

Request

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.