Read a project's monitoring config
GET/api/v1/projects/:project_id/monitoring
The embedded monitoring config : enabled flag, interval, the
auto-enrolled MonitorCheck list, and the server-computed
next_run_at / last_run_at. Never flag-gated — a project that
never configured monitoring returns a disabled, empty default.
Also carries monitorable_count — the LIVE count of
currently-enrollable finding_poc checks, computed read-only from the
project's confirmed / fixed black-box findings WITHOUT persisting. This is
the authoritative "is there anything to probe right now?" signal the
Monitoring tab gates on, so a source-less black-box project whose finding
just qualified can reach the enable form before any config write has
refreshed the persisted checks list.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
- 429
- 500
Successful Response
Bad request — malformed input or failed validation.
Missing, expired, or invalid credentials.
Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.
Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).
Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).
Semantic validation failure — request shape was valid but contents were not.
Too many requests — rate limited. Retry after the window resets.
Internal server error — unexpected failure.