Create a scan schedule

POST 
/api/v1/projects/:project_id/schedules

Add a recurring scan schedule to the project.

• Enum cadence only (weekly / biweekly / monthly + weekday / day-of-month + hour_utc); next_run_at is server-computed.
• Validated against the assessment registry: a sourceless project cannot schedule a code audit (project_has_no_source); a black-box schedule requires configured blackbox_config target URLs.
• Gated by the admission-only release_scheduled_scans flag (404 when off) — the same flag the materializer checks before creating runs. Existing schedules stay readable/editable when it flips off.
• 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.