Configure a project's monitoring

PUT 
/api/v1/projects/:project_id/monitoring

Toggle monitoring + set the cadence.

• enabled + interval_days are the only client-owned knobs; the checks list is server-maintained (auto-enrolled from the project's confirmed / fixed black-box findings, refreshed on every config write).
• Admission: ENABLING monitoring requires the release_monitoring flag (404 when off) — the same flag the materializer's monitoring source checks. Disabling is never gated, so flipping the flag off strands nothing.
• Enabling with zero enrolled checks is rejected with 400 project_monitoring_no_checks — nothing to probe means a materialized run does no work; confirm a black-box finding first.
• 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.