# List scanner filter options

Scanner dropdown for scan-history and findings filters: array of {id: product.name, prettyName}. With targetId and/or targetVariantId, scanners come from execution_summary grains (same candidate set as ListTargetExecutions). With executionId, that set is limited to one execution. With none of those, flatten project target_summary.scan_type_scanners. FE shows prettyName and sends id as scanners query param.

Endpoint: GET /sto/api/v2/targets/filter/scanners
Version: 1.0
Security: 

## Query parameters:

  - `accountId` (string, required)
    Harness Account ID
    Example: "abcdef1234567890ghijkl"

  - `orgId` (string, required)
    Harness Organization ID
    Example: "example_org"

  - `projectId` (string, required)
    Harness Project ID
    Example: "example_project"

  - `targetId` (string)
    Optional target id. When set, scanners are those on execution_summary rows for this target.
    Example: "abcdef1234567890ghijkl"

  - `targetVariantId` (string)
    Optional variant id. When set, scanners are those on execution_summary rows for this variant. Combined with targetId, the variant must belong to the target.
    Example: "xyz987zyx654wvu321tsr9"

  - `executionId` (string)
    Harness Execution ID
    Example: "abcdef1234567890ghijkl"

## Response 200 fields (application/json):

  - `id` (string, required)
    Scanner product name used as the filter id
    Example: "trivy"

  - `prettyName` (string, required)
    Scanner display name (product.prettyName, falling back to product name)
    Example: "Trivy"

## Response 400 fields (application/json):

  - `message` (string, required)
    Example: "Not Found"

  - `status` (integer)
    Example: 404