List Targets

Fields to exclude from the response.

Names of the teams to exclude from results, as a query string.
For example, "exclude_team=Frontend" or "exclude_team=Frontend&exclude_team=Backend".

Identifiers of targets to filter results. Multiple choices are possible by repeating the query_param.

If true, triggers custom response for id filter validation.
If any id filter is invalid, returns a 404 with the following content:

{
    "detail": "Not Found",
    "is_id_404_validation": true,
    "invalid_ids": [
        "9vebyEVLNoZX",
        "6CuzJtJmMp48"
    ]
}

Target label IDs to filter results, as a query string.

Logical operator to apply between target labels.
(Defaults to or)

• and - and
• or - or

Number of results to return per page.

Which field to use when ordering the results.
Ascending order is the default. For descending order, prefix the field with -.
For example, latest_scan_date and -latest_scan_date.
Field to order by:

• target__name
• risk
• latest_scan_date
• changed
• name

A page number within the paginated result set.

Target risk to filter results:

• None - Not applicable.
• 0 - No risk.
• 10 - Low risk.
• 20 - Medium risk.
• 30 - High risk.
• 40 - Critical risk.

Identifier of the scan profile to filter results.

A search term.

Names of the teams to filter results, as a query string.
For example, "team=Frontend" or "team=Frontend&team=Backend".

Type of target to filter results.
Possible values are "single" for a web application and "api" for an API.

If true, filter results by targets with unlimited scans.
If false, filter results by targets that use credits.

If true, filter results by verified targets.
If false, filter results by unverified targets.